crashing

General support regarding TimeTrex, such as
configuring policies/taxes or processing payroll.
Post Reply
jp7290
Posts: 3
Joined: Mon Dec 06, 2021 9:23 am

crashing

Post by jp7290 »

I am using the TimeTrex Community Edition OnSite.
Since the upgrade last week users have a problem when clocking in.
At times they just get a Processing on the screen.
Sometimes it takes there clock in time and sometimes it does not.
Tried running payroll today and keep getting the same thing.
Have been trying to do aa payroll report to verify times for almost two hours now.
shaunw
Posts: 7839
Joined: Tue Sep 19, 2006 2:22 pm

Re: crashing

Post by shaunw »

Please see this FAQ for instructions on how to provide more information:
viewtopic.php?t=89
jp7290
Posts: 3
Joined: Mon Dec 06, 2021 9:23 am

Re: crashing

Post by jp7290 »

Windows 10 machine with current updates installed.
Running TimeTrex Community Edition ver. 15
This started after auto update to ver. 15


Logged in as RBAdmin which is the administrator account.
Trying to run report and it sits on Processing for a while and then sometimes it works and others it just closes the program.
This time recreating for upload it took 4 minutes before opening up report.
Diagnostics uploaded.
Registration Key last 6: 0754c9
Attachments
screen capture.JPG
jp7290
Posts: 3
Joined: Mon Dec 06, 2021 9:23 am

Re: crashing

Post by jp7290 »

Forgot to add:

Does the same thing when either using Google Chrome or Microsoft Edge.
Diagnostic data was using Google Chrome.
shaunw
Posts: 7839
Joined: Tue Sep 19, 2006 2:22 pm

Re: crashing

Post by shaunw »

According to the log, everything is working correctly, albeit extremely slow. Operations that should take just a few milliseconds are taking hundreds in some cases, then immediately after taking tens of thousands.

For example, below are requests about 2 minutes apart and you will notice the "setTimeZone" line took 39ms, 252ms and 28882ms in each case respectively. This is a basic operation where TimeTrex tells the operating system which time zone to use, so the fact that it ranges from 39ms to 28882ms within minutes of each other has nothing to do with TimeTrex itself.

Code: Select all

---------------[ 1639081299.1064 {09-Dec-2021 15:21:39 -0500} (PID: 13208) ]---------------
DEBUG [L0448] [00001ms]: GLOBAL: URI: /api/json/api.php?Class=APIPunch&Method=getUserPunch&v=2&user_id=05b9e1d6-fa9a-4d32-cfa3-38eae9380795&StationID=e169dd77033cd4d469ff6d70fb21edea&MessageID=11ec592d-99ac-0988-8b22-fa9a4d32cfa3 IP Address: 10.115.88.213
DEBUG [L0449] [00001ms]: GLOBAL: USER-AGENT: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36
DEBUG [L0450] [00001ms]: GLOBAL: Version: 15.0.0 (PHP: v7.4.5 [8]) Edition: 10 Production: 1 Server: 10.115.89.9 OS: WIN Database: Type: postgres8 Name: timetrex Config: C:\TimeTrex\timetrex\includes\..\timetrex.ini.php Demo Mode: 0
DEBUG [L0353] [00039ms]: TTDate::setTimeZone(): Setting TimeZone: America/New_York

Code: Select all

---------------[ 1639081374.3796 {09-Dec-2021 15:22:54 -0500} (PID: 12756) ]---------------
DEBUG [L0448] [00001ms]: GLOBAL: URI: /api/json/api.php?Class=APITimesheetDetailReport&Method=getOptions&v=2&MessageID=11ec592d-ca45-0186-8da1-5a7282834165 IP Address: 10.115.89.9
DEBUG [L0449] [00001ms]: GLOBAL: USER-AGENT: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36
DEBUG [L0450] [00002ms]: GLOBAL: Version: 15.0.0 (PHP: v7.4.5 [8]) Edition: 10 Production: 1 Server: 10.115.89.9 OS: WIN Database: Type: postgres8 Name: timetrex Config: C:\TimeTrex\timetrex\includes\..\timetrex.ini.php Demo Mode: 0
DEBUG [L0353] [00251ms]: TTDate::setTimeZone(): Setting TimeZone: America/New_York

Code: Select all

---------------[ 1639081374.6434 {09-Dec-2021 15:23:23 -0500} (PID: 12756) ]---------------
DEBUG [L0448] [00001ms]: GLOBAL: URI: /api/json/api.php?Class=APITimesheetDetailReport&Method=getOptions&v=2&MessageID=11ec592d-ca45-0186-8da1-5a7282834165 IP Address: 10.115.89.9
DEBUG [L0449] [00001ms]: GLOBAL: USER-AGENT: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36
DEBUG [L0450] [00001ms]: GLOBAL: Version: 15.0.0 (PHP: v7.4.5 [8]) Edition: 10 Production: 1 Server: 10.115.89.9 OS: WIN Database: Type: postgres8 Name: timetrex Config: C:\TimeTrex\timetrex\includes\..\timetrex.ini.php Demo Mode: 0
DEBUG [L0353] [28882ms]: TTDate::setTimeZone(): Setting TimeZone: America/New_York
My best guess is something is running on your TimeTrex server that is either overloading the system or severely slowing it down. Virus/malware scanners are often the first culprits to investigate.
Post Reply