power outage now down for maintenance

centaur5 · Post by **centaur5** » Sun Mar 30, 2008 8:13 pm

I'm using Ubuntu 7.10, apache2, and postgresql 8.3.

Weather caused the power to go out longer than the battery backups last and now Timetrex will start but it complains saying:

pg_ctl.bin: another server may be running; trying to start server anyway
pg_ctl.bin: could not start server
Examine the log output.

Here is the log output:

---------------[ Sun, 30 Mar 2008 19:58:57 -0600 (PID: 8589) ]---------------
DEBUG [259]: [Function](): URI: /interface/ 
DEBUG [261]: [Function](): Version: 2.2.7 Edition: 10 Production: 1 De
mo Mode: 0 
DEBUG [73]: [Function](): Error connecting to the database! 
DEBUG [39]: DBError::__construct(): postgres7 error: [-1: Database co
nnection failed] in CONNECT(localhost:5433, 'timetrex', '****', timetrex)
 
---------------[ Sun, 30 Mar 2008 19:58:57 -0600 (PID: 8589) ]---------------
---------------[ Sun, 30 Mar 2008 19:58:58 -0600 (PID: 8589) ]---------------
DEBUG [259]: [Function](): URI: /interface/DownForMaintenance.php?exception=DBError 
DEBUG [261]: [Function](): Version: 2.2.7 Edition: 10 Production: 1 Demo Mode: 0 
DEBUG [107]: TTDate::setTimeZone(): Setting TimeZone: America/Denver 
DEBUG [53]: [Function](): Bypassing Authentication 
DEBUG [400]: TTi18n::chooseBestLocale(): Choosing Best Locale... 
DEBUG [371]: TTi18n::getBrowserLanguage(): HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5 
DEBUG [454]: TTi18n::chooseBestLocale(): cSetting Locale: en_US 
DEBUG [318]: TTi18n::setLocale(): Generated/Passed In Locale: en_US 
DEBUG [252]: TTi18n::generateLocale(): Array of Locales to try in order: en_US,en_US.UTF-8,en,en.UTF-8 
DEBUG [211]: TTi18n::tryLocale(): Found valid locale: en_US.UTF-8 
DEBUG [324]: TTi18n::setLocale(): Attempting to set Locale(s) to: en_US.UTF-8 Category: 6 Current Locale: 
DEBUG [327]: TTi18n::setLocale(): Setting currency/numeric Locale to: en_US.UTF-8 
DEBUG [340]: TTi18n::setLocale(): Setting translator locale to: en_US 
DEBUG [357]: TTi18n::setLocale(): Set Master Locale To: en_US.UTF-8 
DEBUG [463]: TTi18n::chooseBestLocale(): Using Locale: en_US.UTF-8 
---------------[ Sun, 30 Mar 2008 19:58:58 -0600 (PID: 8589) ]---------------
---------------[ Sun, 30 Mar 2008 19:58:58 -0600 (PID: 8589) ]---------------
DEBUG [259]: [Function](): URI: /interface//send_file.php?object_type=primary_company_logo 
DEBUG [261]: [Function](): Version: 2.2.7 Edition: 10 Production: 1 Demo Mode: 0 
DEBUG [73]: [Function](): Error connecting to the database! 
DEBUG [39]: DBError::__construct(): postgres7 error: [-1: Database connection failed] in CONNECT(localhost:5433, 'timetrex', '****', timetrex)
 
---------------[ Sun, 30 Mar 2008 19:58:58 -0600 (PID: 8589) ]---------------
---------------[ Sun, 30 Mar 2008 19:58:59 -0600 (PID: 8589) ]---------------
DEBUG [259]: [Function](): URI: /interface/DownForMaintenance.php?exception=DBError 
DEBUG [261]: [Function](): Version: 2.2.7 Edition: 10 Production: 1 Demo Mode: 0 
DEBUG [107]: TTDate::setTimeZone(): Setting TimeZone: America/Denver 
DEBUG [53]: [Function](): Bypassing Authentication 
DEBUG [400]: TTi18n::chooseBestLocale(): Choosing Best Locale... 
DEBUG [371]: TTi18n::getBrowserLanguage(): HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5 
DEBUG [454]: TTi18n::chooseBestLocale(): cSetting Locale: en_US 
DEBUG [318]: TTi18n::setLocale(): Generated/Passed In Locale: en_US 
DEBUG [252]: TTi18n::generateLocale(): Array of Locales to try in order: en_US,en_US.UTF-8,en,en.UTF-8 
DEBUG [211]: TTi18n::tryLocale(): Found valid locale: en_US.UTF-8 
DEBUG [324]: TTi18n::setLocale(): Attempting to set Locale(s) to: en_US.UTF-8 Category: 6 Current Locale: 
DEBUG [327]: TTi18n::setLocale(): Setting currency/numeric Locale to: en_US.UTF-8 
DEBUG [340]: TTi18n::setLocale(): Setting translator locale to: en_US 
DEBUG [357]: TTi18n::setLocale(): Set Master Locale To: en_US.UTF-8 
DEBUG [463]: TTi18n::chooseBestLocale(): Using Locale: en_US.UTF-8 
---------------[ Sun, 30 Mar 2008 19:58:59 -0600 (PID: 8589) ]---------------

Post by **shaunw** » Sun Mar 30, 2008 8:32 pm

The issue is with your database.

Try stopping it and starting it again. You may have to remove the .PID file so it can start cleanly again if the server wasn't shut down properly.

centaur5 · Post by **centaur5** » Sun Mar 30, 2008 8:48 pm

Thanks for the fast reply. When I tried stopping it I was constantly getting an error so I deleted the .pid file as you suggested and now it started successfully. Now that I'm almost done configuring everything I'm a little worried about losing the data I input. The maintenance jobs aren't running although I did run the ./install_cron script so I'm wondering if there is something else I'm supposed to do to make those jobs run? Most forums I searched everybody is using windows so I haven't found anything to help me with this problem.

Post by **shaunw** » Mon Mar 31, 2008 10:27 am

If you run:

crontab -e

as the user you installed TimeTrex as, do you see a line in their that belongs to TimeTrex? If so, what is it?

centaur5 · Post by **centaur5** » Mon Mar 31, 2008 10:45 am

I noticed that the install_cron script wasn't successfully writing to the user's crontab for some reason and it was putting a file in /tmp instead. I then copied and pasted the line that was recorded in that file into my user's crontab. I now have the following when I do crontab -e:

* * * * * /opt/timetrex/TimeTrex/php/bin/php /opt/timetrex/TimeTrex/timetrex/maint/cron.php >> /dev/null 2>&1

Does it take time for the first maintenance job to run cause if I understand correctly it's supposed to be running every minute? I still have the warning that the jobs aren't running though.

Post by **shaunw** » Mon Mar 31, 2008 11:41 am

In some cases it can take 24-48hrs for the warning to disappear.

I would try running this command manually as the user you installed TimeTrex as:

Code: Select all

/opt/timetrex/TimeTrex/php/bin/php /opt/timetrex/TimeTrex/timetrex/maint/cron.php

Does it return any output?

centaur5 · Post by **centaur5** » Mon Mar 31, 2008 11:42 am

Result of that line is:

NOTE: Jobs are scheduled to run at specific times, therefore only some jobs are executed each time this file is run.
Jobs Executed: 0 of 11

Post by **shaunw** » Mon Mar 31, 2008 3:27 pm

Okay, so that looks normal.

I would just check your crontab logs to ensure that it is in fact executing that command each minute and if so the error message should disappear in 24hours or so.

centaur5 · Post by **centaur5** » Tue Apr 01, 2008 10:38 am

Maintenance error messages do not show up today so it appears everything is working perfectly. Thanks for your help!

TimeTrex Time and Attendance

power outage now down for maintenance

power outage now down for maintenance

Time and Attendance