Good Morning,
yesterday I tried to update Safelinx from 1.4.2 to 1.4.3.
The update process has been completed, but the http service does not start.
After that I decided to reload my snapshot.
So I cannot provide any logfiles now.
The OS is CentOS Linux release 7.9.2009 (Core).
Any ideas?
Regards
Hubertus
It'll be hard to say what is causing the error. Was there any chance you are able to copy the wg.log?
https://help.hcl-software.com/safelinx/1.3/troubleshooting/cmprob.html
Hi Jessie,
I ran the update again. Same problem.
Can't attache logs here. Greater than 2 MB. ;-/
Hubertus
maybe just copy some few lines from wg.log.
Ok,
here are some parts from the end of wg.log:
19638:156546816 (Sep 27 2024/10:08:40.0004)[STATUS]Session database pool idle connections: 1
19638:156546816 (Sep 27 2024/10:08:40.0005)[STATUS]DataSystem: Total buffers: 100 Free: 99 Queue Size: 1
19638:156546816 (Sep 27 2024/10:08:40.0007)[STATUS]DataSystem: Memory Allocation: arena=123.0 MB, inuse=26.2 MB, freeblks=96.8 MB
19638:156546816 (Sep 27 2024/10:08:40.0009)[LOG] HTTP_Listener::monitor: (entry)
19638:156546816 (Sep 27 2024/10:08:40.0010)[LOG] HTTP_Listener::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:08:40.0011)[LOG] nomad-web-proxy0::monitor: (entry)
19638:156546816 (Sep 27 2024/10:08:40.0013)[STATUS]nomad-web-proxy0: state: Active, cons: 0, failed cons: 0 file:///srv/hcl
19638:156546816 (Sep 27 2024/10:08:40.0014)[STATUS]nomad-web-proxy0: state: Active, cons: 0, failed cons: 0 file:///opt/hcl/SafeLinx/saml
19638:156546816 (Sep 27 2024/10:08:40.0015)[LOG] nomad-web-proxy0::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:08:40.0016)[DEBUG] Gateway::monitor: active session table processed in 0 ms
19638:156546816 (Sep 27 2024/10:08:40.0017)[S-AUTH]AUTH_LdapBind: total records on queue 0
19638:156546816 (Sep 27 2024/10:08:40.0020)[STATUS]Thruput analysis
System Load: 0.0600 0.2000 0.2100
Active Sessions: 0 Activation Rate: 0.00
19638:156546816 (Sep 27 2024/10:08:55.0004)[STATUS]Session database pool idle connections: 1
19638:156546816 (Sep 27 2024/10:08:55.0005)[STATUS]DataSystem: Total buffers: 100 Free: 99 Queue Size: 1
19638:156546816 (Sep 27 2024/10:08:55.0007)[STATUS]DataSystem: Memory Allocation: arena=123.0 MB, inuse=26.2 MB, freeblks=96.8 MB
19638:156546816 (Sep 27 2024/10:08:55.0008)[LOG] HTTP_Listener::monitor: (entry)
19638:156546816 (Sep 27 2024/10:08:55.0009)[LOG] HTTP_Listener::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:08:55.0010)[LOG] nomad-web-proxy0::monitor: (entry)
19638:156546816 (Sep 27 2024/10:08:55.0011)[LOG] nomad-web-proxy0::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:08:55.0012)[DEBUG] Gateway::monitor: active session table processed in 0 ms
19638:156546816 (Sep 27 2024/10:08:55.0013)[S-AUTH]AUTH_LdapBind: total records on queue 0
19638:156546816 (Sep 27 2024/10:08:55.0016)[STATUS]Thruput analysis
System Load: 0.1200 0.2100 0.2200
Active Sessions: 0 Activation Rate: 0.00
19638:4179707648 (Sep 27 2024/10:09:05.5719)[DEBUG] Timer: handling timeout event
19638:4179707648 (Sep 27 2024/10:09:05.5720)[DEBUG] Timer: next alarm scheduled for 10 seconds
19638:4179707648 (Sep 27 2024/10:09:05.5721)[DEBUG] Executing timer id 15
19638:4179707648 (Sep 27 2024/10:09:05.5722)[DEBUG] Done with timer '15'
19638:156546816 (Sep 27 2024/10:09:10.0003)[STATUS]Session database pool idle connections: 1
19638:156546816 (Sep 27 2024/10:09:10.0004)[STATUS]DataSystem: Total buffers: 100 Free: 99 Queue Size: 1
19638:156546816 (Sep 27 2024/10:09:10.0006)[STATUS]DataSystem: Memory Allocation: arena=123.0 MB, inuse=26.2 MB, freeblks=96.8 MB
19638:156546816 (Sep 27 2024/10:09:10.0008)[LOG] HTTP_Listener::monitor: (entry)
19638:156546816 (Sep 27 2024/10:09:10.0009)[LOG] HTTP_Listener::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:09:10.0009)[LOG] nomad-web-proxy0::monitor: (entry)
19638:156546816 (Sep 27 2024/10:09:10.0010)[LOG] nomad-web-proxy0::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:09:10.0012)[DEBUG] Gateway::monitor: active session table processed in 0 ms
19638:156546816 (Sep 27 2024/10:09:10.0012)[S-AUTH]AUTH_LdapBind: total records on queue 0
19638:156546816 (Sep 27 2024/10:09:10.0014)[STATUS]Thruput analysis
System Load: 0.0900 0.2000 0.2100
Active Sessions: 0 Activation Rate: 0.00
19638:4179707648 (Sep 27 2024/10:09:15.5722)[DEBUG] Timer: handling timeout event
19638:4179707648 (Sep 27 2024/10:09:15.5723)[DEBUG] Timer: next alarm scheduled for 50 seconds
19638:4179707648 (Sep 27 2024/10:09:15.5724)[DEBUG] Executing timer id 4
19638:4179707648 (Sep 27 2024/10:09:15.5746)[DEBUG] Timer: next alarm scheduled for 7 seconds
19638:4179707648 (Sep 27 2024/10:09:15.5747)[DEBUG] DBManager::process - wgdata Inactive Connection Timer reset to 7 seconds
19638:4179707648 (Sep 27 2024/10:09:15.5747)[DEBUG] Done with timer '4'
19638:4179707648 (Sep 27 2024/10:09:22.5747)[DEBUG] Timer: handling timeout event
19638:4179707648 (Sep 27 2024/10:09:22.5749)[DEBUG] Timer: next alarm scheduled for 43 seconds
19638:4179707648 (Sep 27 2024/10:09:22.5751)[DEBUG] Executing timer id 17
19638:4179707648 (Sep 27 2024/10:09:22.5772)[LOG] DBManager::process - wgdata - Handling inactive connection timer by suspending the database connection
19638:4179707648 (Sep 27 2024/10:09:22.5773)[DEBUG] DBManager::process - wgdata: closing table handles
19638:4179707648 (Sep 27 2024/10:09:22.5774)[LOG] DBManager::disconnect - wgdata: (entry)
19638:4179707648 (Sep 27 2024/10:09:22.5775)[DEBUG] DBManager::disconnect - wgdata Inactive Connection Timer stopped!
19638:4179707648 (Sep 27 2024/10:09:23.3243)[LOG] DBManager::disconnect - wgdata: (return), rc=0
19638:4179707648 (Sep 27 2024/10:09:23.3244)[DEBUG] Done with timer '17'
19638:156546816 (Sep 27 2024/10:09:25.0003)[STATUS]Session database pool idle connections: 1
19638:156546816 (Sep 27 2024/10:09:25.0004)[STATUS]DataSystem: Total buffers: 100 Free: 99 Queue Size: 1
19638:156546816 (Sep 27 2024/10:09:25.0005)[STATUS]DataSystem: Memory Allocation: arena=123.0 MB, inuse=26.2 MB, freeblks=96.8 MB
19638:156546816 (Sep 27 2024/10:09:25.0007)[LOG] HTTP_Listener::monitor: (entry)
19638:156546816 (Sep 27 2024/10:09:25.0008)[LOG] HTTP_Listener::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:09:25.0009)[LOG] nomad-web-proxy0::monitor: (entry)
19638:156546816 (Sep 27 2024/10:09:25.0010)[LOG] nomad-web-proxy0::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:09:25.0011)[DEBUG] Gateway::monitor: active session table processed in 0 ms
19638:156546816 (Sep 27 2024/10:09:25.0012)[S-AUTH]AUTH_LdapBind: total records on queue 0
19638:156546816 (Sep 27 2024/10:09:25.0014)[STATUS]Thruput analysis
System Load: 0.0700 0.1900 0.2100
Active Sessions: 0 Activation Rate: 0.00
19638:156546816 (Sep 27 2024/10:09:40.0002)[STATUS]Session database pool idle connections: 1
19638:156546816 (Sep 27 2024/10:09:40.0003)[STATUS]DataSystem: Total buffers: 100 Free: 99 Queue Size: 1
19638:156546816 (Sep 27 2024/10:09:40.0005)[STATUS]DataSystem: Memory Allocation: arena=123.0 MB, inuse=26.2 MB, freeblks=96.8 MB
19638:156546816 (Sep 27 2024/10:09:40.0005)[LOG] HTTP_Listener::monitor: (entry)
19638:156546816 (Sep 27 2024/10:09:40.0006)[LOG] HTTP_Listener::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:09:40.0006)[LOG] nomad-web-proxy0::monitor: (entry)
19638:156546816 (Sep 27 2024/10:09:40.0007)[STATUS]nomad-web-proxy0: state: Active, cons: 0, failed cons: 0 file:///srv/hcl
19638:156546816 (Sep 27 2024/10:09:40.0007)[STATUS]nomad-web-proxy0: state: Active, cons: 0, failed cons: 0 file:///opt/hcl/SafeLinx/saml
19638:156546816 (Sep 27 2024/10:09:40.0008)[LOG] nomad-web-proxy0::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:09:40.0008)[DEBUG] Gateway::monitor: active session table processed in 0 ms
19638:156546816 (Sep 27 2024/10:09:40.0009)[S-AUTH]AUTH_LdapBind: total records on queue 0
19638:156546816 (Sep 27 2024/10:09:40.0010)[STATUS]Thruput analysis
System Load: 0.0600 0.1800 0.2100
Active Sessions: 0 Activation Rate: 0.00
19638:156546816 (Sep 27 2024/10:09:55.0004)[STATUS]Session database pool idle connections: 1
19638:156546816 (Sep 27 2024/10:09:55.0005)[STATUS]DataSystem: Total buffers: 100 Free: 99 Queue Size: 1
19638:156546816 (Sep 27 2024/10:09:55.0006)[STATUS]DataSystem: Memory Allocation: arena=123.0 MB, inuse=26.2 MB, freeblks=96.8 MB
19638:156546816 (Sep 27 2024/10:09:55.0007)[LOG] HTTP_Listener::monitor: (entry)
19638:156546816 (Sep 27 2024/10:09:55.0008)[LOG] HTTP_Listener::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:09:55.0009)[LOG] nomad-web-proxy0::monitor: (entry)
19638:156546816 (Sep 27 2024/10:09:55.0010)[LOG] nomad-web-proxy0::monitor: (return), rc=0
19638:156546816 (Sep 27 2024/10:09:55.0011)[DEBUG] Gateway::monitor: active session table processed in 0 ms
19638:156546816 (Sep 27 2024/10:09:55.0011)[S-AUTH]AUTH_LdapBind: total records on queue 0
19638:156546816 (Sep 27 2024/10:09:55.0013)[STATUS]Thruput analysis
System Load: 0.0400 0.1700 0.2000
Active Sessions: 0 Activation Rate: 0.00
Hi Hubertus. Please can you open a support case for us to investigate the issue? Thanks.
Hello Analyn,
yes, I can do that in 2 weeks.
After my vacation.
I will restore the snapshot now.
Many thanks and kind regards
Hubertus
Hello Hubertus,
Looking at the screenshot, the issue observed when adding/updating any of the SafeLinx service via Administrator.
To get more details, can you please share us the recent contents of /var/adm/wgmgrd.log file ?
Hello Hubertus,
Looking at the screenshot, the issue observed when adding/updating any of the SafeLinx service via Administrator.
To get more details, can you please share us the recent contents of /var/adm/wgmgrd.log file ?
Hello,
Thank you for the reply.
Do you have access to DB2 database, if so, can you execute below command and see how SafeLinx working after this change ?
CONNECT TO WGDATA;
ALTER TABLE WG.WLRESOURCE ALTER COLUMN DATUM SET DATA TYPE VARCHAR(7999);
Our purpose is to update the DATUM column size to maximum supported (currently we kept as 7999). Even if my command fails, can you try to update the DATUM column size in WLRESOURCE table in WGDATA database to 7999.
Regards,
Kandarpa
