After some review of the source code, I'm unable to locate where or the
conditions which would instantiate:
org.apache.roller.weblogger.ui.struts2.core.Install
Would you or someone else please confirm? Also, looking that the source
code for that same class:
/**
* Walk user through install process.
*/
// TODO: make this work
@AllowedMethods({"execute","create","upgrade","bootstrap"})
public class Install extends UIAction {
Am I correct to assume that the installation process isn't quite complete?
Thank you,
Tommy
On Fri, Feb 7, 2020 at 2:12 PM Tommy Pham <[email protected]> wrote:
> Hi Dave,
>
> After some more thought about the application startup process, I decided
> to change the DB password to an invalid one to force an expected error
> which it did. I also tried changing the installation type from auto to
> manual and use the provided MySQL script in dbscripts to create the
> schema. It still failed with the same error in Tomcat and no error within
> the roller's log. I suspect that either or both of the:
>
> org.apache.roller.weblogger.business.startup.WebloggerStartup
> org.apache.roller.weblogger.business.startup.DatabaseInstaller
>
> is/are failing because the schema was not created for auto installation
> type or it failed to detect the schema for manual despite the successful
> test DB connection within:
>
> org.apache.roller.weblogger.business.DatabaseProvider
>
> Thanks,
> Tommy
>
>
> On Fri, Feb 7, 2020 at 1:13 PM Tommy Pham <[email protected]> wrote:
>
>> Hi Dave,
>>
>> Thanks for the feedback. Here is the log for both Tomcat and Roller:
>> https://pastebin.com/PCjF024T
>>
>> I've just tried a clone from the current github with the same result.
>> The only thing I could think of is roller failing silently somewhere but I
>> don't know where to start checking.
>>
>> Thanks,
>> Tommy
>>
>> On Fri, Feb 7, 2020 at 5:03 AM Dave <[email protected]> wrote:
>>
>>> Hi Tommy,
>>>
>>> I don't think this mailing list allows attachments. Can you please make
>>> your logs available somewhere, like a GitHib gist or a past bin so we can
>>> see them. Both the Tomcat and roller.log logs might be useful.
>>>
>>> Thanks,
>>> Dave
>>>
>>>
>>> On Fri, Feb 7, 2020 at 1:52 AM Tommy Pham <[email protected]> wrote:
>>>
>>> > Hello everyone,
>>> >
>>> > I'm having problems installing Roller 6 in the new Tomcat environment:
>>> >
>>> > OS: FreeBSD 12.1-RELEASE
>>> > JDK: OpenJDK 11.0.6
>>> > Web Container: Tomcat 9.0.30
>>> > DB: MariaDB 10.4.12
>>> > JDBC client: MariaDB Java client 2.5.4
>>> >
>>> > My roller-custom.properties:
>>> >
>>> > installation.type=auto
>>> > database.configurationType=jdbc
>>> > database.jndi.name=jdbc/rollerdb
>>> > database.jdbc.driverClass=org.mariadb.jdbc.Driver
>>> >
>>> >
>>> database.jdbc.connectionURL=jdbc:mysql://x.x.x.x:3306/roller?autoReconnect=true&useUnicode=true&characterEncoding=utf-8&mysqlEncoding=utf8
>>> > database.jdbc.username=roller
>>> > database.jdbc.password=xxx
>>> > mail.configurationType=properties
>>> > mail.jndi.name=mail/Session
>>> > mail.hostname=x.x.x
>>> >
>>> mediafiles.storage.dir=/usr/local/www/_apps_/java/roller6_data/mediafiles
>>> > search.index.dir=/usr/local/www/_apps_/java/roller6_data/search-index
>>> > log4j.rootLogger=DEBUG, roller
>>> > log4j.logger.org.apache.roller=DEBUG
>>> > log4j.logger.net.java.roller=DEBUG
>>> >
>>> > (log4j were added to troubleshoot this which didn't provide any
>>> insight).
>>> > Attached is the Tomcat + roller logs. Tomcat reports SEVERE error
>>> starting
>>> > context /blogger and suggested to look inside the container's log.
>>> > However, roller's log didn't show any error. I've also check the
>>> database
>>> > logs for any errors but none found. Does anyone have any suggestions
>>> on
>>> > where I can look to investigate further?
>>> >
>>> > TIA,
>>> > Tommy
>>> >
>>>
>>
