Installation successful but now doesn't even log in

Ask your questions regarding TimeTrex installation here.
Post Reply
roddydairion
Posts: 5
Joined: Mon Sep 14, 2015 7:14 am

Installation successful but now doesn't even log in

Post by roddydairion »

Hi I've installed the timetrex on a Centos Machine. The installation was successful but when I enter the username and password, nothing is happening. I don't get a redirect or a processing icon.

Can anybody help with this please?

Regards,
Roddy
shaunw
Posts: 7839
Joined: Tue Sep 19, 2006 2:22 pm

Re: Installation successful but now doesn't even log in

Post by shaunw »

roddydairion
Posts: 5
Joined: Mon Sep 14, 2015 7:14 am

Re: Installation successful but now doesn't even log in

Post by roddydairion »

Hi again,

The timetrex version is 8.0.9 on a CentOS release 6.7, I installed timetrex using the zip file provided for linux. I have Apache installed with PHP 5.3.3, along with MySQL 5.1.73.

Ok I've installed everything as requested by the installation wizard.

When I load my url to access the page http://127.0.0.1/timetrex/interface/html5/, I get the login screen, I entered my administrator username name and password. It didn't look like it was processing anything, it just stayed there.

I've restarted my server. I know get the initialisation bar, I then get a process pop up, and then a grey screen. Please find attached screenshots in zip file. My timetrex log file is currently displaying this
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): PHP ERROR - WARNING(2): mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Etc/GMT-4' for 'GMT-4/4.0/no DST' instead File: /var/www/html/timetr
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): ex/classes/modules/core/TTDate.class.php Line: 892
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): #0.Debug::backTrace()
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): #1.Debug::ErrorHandler(2, mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case y
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): ou used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Etc/GMT-4' for 'GMT-4/4.0/no DST' instead, /var/www/html/timetrex/
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): classes/modules/core/TTDate.class.php, 892, Array(5))
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): #2.mktime(2, 59, 0, 9, 15, 2015)
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): #3.TTDate::incrementDate(1442267940, 1, hour)
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): #4.Cron::getNextScheduleDate(59, 2, *, *, *, 1442240580)
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): #5.Cron::isScheduledToRun(59, 2, *, *, *, 1442242201, 1442240580)
DEBUG [L0892] [891ms]: Debug::ErrorHandler(): #6.CronJobFactory->isScheduledToRun(1442242201)
DEBUG [L0892] [891ms]: Debug::ErrorHandler():
DEBUG [L0199] [891ms]: Debug::ErrorHandler(): PHP ERROR - WARNING(2): getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case yo
DEBUG [L0199] [891ms]: Debug::ErrorHandler(): u used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Etc/GMT-4' for 'GMT-4/4.0/no DST' instead File: /var/www/html/timet
DEBUG [L0199] [891ms]: Debug::ErrorHandler(): rex/classes/modules/cron/Cron.class.php Line: 199
DEBUG [L0199] [891ms]: Debug::ErrorHandler(): #0.Debug::backTrace()
DEBUG [L0199] [891ms]: Debug::ErrorHandler(): #1.Debug::ErrorHandler(2, getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case
DEBUG [L0199] [891ms]: Debug::ErrorHandler(): you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Etc/GMT-4' for 'GMT-4/4.0/no DST' instead, /var/www/html/timetrex
DEBUG [L0199] [891ms]: Debug::ErrorHandler(): /classes/modules/cron/Cron.class.php, 199, Array(15))
DEBUG [L0199] [891ms]: Debug::ErrorHandler(): #2.getdate(1442271540)
DEBUG [L0199] [891ms]: Debug::ErrorHandler(): #3.Cron::getNextScheduleDate(59, 2, *, *, *, 1442240580)
DEBUG [L0199] [891ms]: Debug::ErrorHandler(): #4.Cron::isScheduledToRun(59, 2, *, *, *, 1442242201, 1442240580)
DEBUG [L0199] [891ms]: Debug::ErrorHandler(): #5.CronJobFactory->isScheduledToRun(1442242201)
DEBUG [L0199] [891ms]: Debug::ErrorHandler():
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): PHP ERROR - WARNING(2): date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you u
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): sed any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Etc/GMT-4' for 'GMT-4/4.0/no DST' instead File: /var/www/html/timetrex
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): /classes/modules/core/TTDate.class.php Line: 692
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #0.Debug::backTrace()
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #1.Debug::ErrorHandler(2, date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Etc/GMT-4' for 'GMT-4/4.0/no DST' instead, /var/www/html/timetrex/cl
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): asses/modules/core/TTDate.class.php, 692, Array(2))
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #2.date(d-M-y g:i A T, 1442271540)
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #3.TTDate::getDate(DATE+TIME, 1442271540)
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #4.Cron::getNextScheduleDate(59, 2, *, *, *, 1442240580)
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #5.Cron::isScheduledToRun(59, 2, *, *, *, 1442242201, 1442240580)
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #6.CronJobFactory->isScheduledToRun(1442242201)
DEBUG [L0692] [891ms]: Debug::ErrorHandler():
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): PHP ERROR - WARNING(2): date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you u
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): sed any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Etc/GMT-4' for 'GMT-4/4.0/no DST' instead File: /var/www/html/timetrex
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): /classes/modules/core/TTDate.class.php Line: 692
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #0.Debug::backTrace()
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #1.Debug::ErrorHandler(2, date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Etc/GMT-4' for 'GMT-4/4.0/no DST' instead, /var/www/html/timetrex/cl
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): asses/modules/core/TTDate.class.php, 692, Array(2))
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #2.date(d-M-y g:i A T, 1442240580)
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #3.TTDate::getDate(DATE+TIME, 1442240580)
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #4.Cron::getNextScheduleDate(59, 2, *, *, *, 1442240580)
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #5.Cron::isScheduledToRun(59, 2, *, *, *, 1442242201, 1442240580)
DEBUG [L0692] [891ms]: Debug::ErrorHandler(): #6.CronJobFactory->isScheduledToRun(1442242201)
DEBUG [L0692] [891ms]: Debug::ErrorHandler():
DEBUG [L0232] [891ms]: Cron::getNextScheduleDate(): Next Scheduled Date: 15-Sep-15 2:59 AM GMT-4 Based on Current Epoch: 14-Sep-15 6:23 PM GMT-4
DEBUG [L0263] [891ms]: Cron::isScheduledToRun(): JOB is NOT scheduled to run right now...
DEBUG [L0072] [891ms]: [Function](): CRON: Jobs Executed: 2 of 16
DEBUG [L0180] [897ms]: Debug::Text(): Detected PHP errors (2531), emailing log...
DEBUG [L0180] [897ms]: Debug::Text(): ---------------[ 14-Sep-2015 18:50:02 +0400 [1442242202.1531] (PID: 15349) ]---------------
DEBUG [L0209] [1241ms] Array: TTMail::Send(): Attempting to send email To:
string(19) "errors@timetrex.com"


DEBUG [L0221] [1241ms]: TTMail::Send(): Sending Email: Body Size: 333307 Method: soap To:
DEBUG [L0263] [1676ms] Array: TTMail::Send(): Send Email Failed To: errors@timetrex.com
bool(false)


DEBUG [L0271] [1676ms] Array: TTMail::Send(): Send Email Failed!
bool(false)


---------------[ 14-Sep-2015 18:50:02 +0400 [1442242202.9354] (PID: 15349) ]---------------

---------------[ 14-Sep-2015 18:59:02 +0400 [1442242741.7682] (PID: 15691) ]---------------
---------------[ 14-Sep-2015 18:59:02 +0400 [1442242742.3766] (PID: 15691) ]---------------

---------------[ 14-Sep-2015 18:59:02 +0400 [1442242741.7682] (PID: 15691) ]---------------
---------------[ 14-Sep-2015 18:59:02 +0400 [1442242742.3789] (PID: 15691) ]---------------

---------------[ 14-Sep-2015 19:00:01 +0400 [1442242801.4232] (PID: 15756) ]---------------
---------------[ 14-Sep-2015 19:00:01 +0400 [1442242801.803] (PID: 15756) ]---------------

---------------[ 14-Sep-2015 19:00:01 +0400 [1442242801.4232] (PID: 15756) ]---------------
---------------[ 14-Sep-2015 19:00:01 +0400 [1442242801.8033] (PID: 15756) ]---------------

---------------[ 14-Sep-2015 19:01:02 +0400 [1442242861.9232] (PID: 15795) ]---------------
---------------[ 14-Sep-2015 19:01:02 +0400 [1442242862.5351] (PID: 15795) ]---------------

---------------[ 14-Sep-2015 19:01:02 +0400 [1442242861.9232] (PID: 15795) ]---------------
---------------[ 14-Sep-2015 19:01:02 +0400 [1442242862.5355] (PID: 15795) ]---------------

---------------[ 14-Sep-2015 19:02:02 +0400 [1442242921.5969] (PID: 15841) ]---------------
---------------[ 14-Sep-2015 19:02:02 +0400 [1442242922.1765] (PID: 15841) ]---------------

---------------[ 14-Sep-2015 19:02:02 +0400 [1442242921.5969] (PID: 15841) ]---------------
---------------[ 14-Sep-2015 19:02:02 +0400 [1442242922.1768] (PID: 15841) ]---------------

---------------[ 14-Sep-2015 19:03:01 +0400 [1442242981.2536] (PID: 15888) ]---------------
---------------[ 14-Sep-2015 19:03:01 +0400 [1442242981.9337] (PID: 15888) ]---------------

---------------[ 14-Sep-2015 19:03:01 +0400 [1442242981.2536] (PID: 15888) ]---------------
---------------[ 14-Sep-2015 19:03:01 +0400 [1442242981.934] (PID: 15888) ]---------------
Attachments
Pictures.zip
Screenshots
(1.02 MiB) Downloaded 374 times
roddydairion
Posts: 5
Joined: Mon Sep 14, 2015 7:14 am

Re: Installation successful but now doesn't even log in

Post by roddydairion »

Fixed it.

I went into my php.ini file

Located the [Date] section, and added my timezone. Restarted httpd, and that worked.

Thanks.
Post Reply