rkomandu
commented
9 months ago noobaa event log on the scale-11 is as follows " Active: active (running) since Thu 2024-01-18 11:11:30 CET; 1h 38min ago"
refer the 11:11:30, nothing special in the below noobaa_events.log
[root@scale-11 log]# less noobaa_events.log
{"timestamp":"2024-01-17T11:11:29.006666+01:00","message":"{\"code\":\"noobaa_started\",\"entity_type\":\"NODE\",\"event_type\":\"STATE_CHANGE\",\"message\":\"Noobaa started\",\"scope\":\"NODE\",\"severity\":\"INFO\",\"state\":\"HEALTHY\",\"pid\":892579}","host":"scale-11","severity":"notice","facility":"local2","syslog-tag":"node[892579]:","source":"node"}
{"timestamp":"2024-01-18T11:12:00.118421+01:00","message":"{\"code\":\"noobaa_started\",\"entity_type\":\"NODE\",\"event_type\":\"STATE_CHANGE\",\"message\":\"Noobaa started\",\"scope\":\"NODE\",\"severity\":\"INFO\",\"state\":\"HEALTHY\",\"pid\":494409}","host":"scale-11","severity":"notice","facility":"local2","syslog-tag":"node[494409]:","source":"node"}
{"timestamp":"2024-01-18T11:27:53.765680+01:00","message":"{\"code\":\"noobaa_account_created\",\"entity_type\":\"NODE\",\"event_type\":\"INFO\",\"message\":\"New noobaa account created.\",\"scope\":\"NODE\",\"severity\":\"INFO\",\"state\":\"HEALTHY\",\"arguments\":{\"account_name\":\"s3user5003@fvt.com\"},\"pid\":494409}","host":"scale-11","severity":"notice","facility":"local2","syslog-tag":"node[494409]:","source":"node"}
{"timestamp":"2024-01-18T11:40:54.840016+01:00","message":"{\"code\":\"noobaa_account_created\",\"entity_type\":\"NODE\",\"event_type\":\"INFO\",\"message\":\"New noobaa account created.\",\"scope\":\"NODE\",\"severity\":\"INFO\",\"state\":\"HEALTHY\",\"arguments\":{\"account_name\":\"s3user5003@fvt.com\"},\"pid\":494409}","host":"scale-11","severity":"notice","facility":"local2","syslog-tag":"node[494409]:","source":"node"}
[root@scale-13 log]# systemctl status noobaa_nsfs
● noobaa_nsfs.service - The NooBaa nsfs service.
Loaded: loaded (/etc/systemd/system/noobaa_nsfs.service; enabled; preset: disabled)
Active: active (running) since Thu 2024-01-18 11:11:30 CET; 1h 39min ago
noobaa_events.log
[root@scale-13 log]# less noobaa_events.log
{"timestamp":"2024-01-17T11:11:29.411330+01:00","message":"{\"code\":\"noobaa_started\",\"entity_type\":\"NODE\",\"event_type\":\"STATE_CHANGE\",\"message\":\"Noobaa started\",\"scope\":\"NODE\",\"severity\":\"INFO\",\"state\":\"HEALTHY\",\"pid\":649898}","host":"scale-13","severity":"notice","facility":"local2","syslog-tag":"node[649898]:","source":"node"}
{"timestamp":"2024-01-18T11:11:56.975086+01:00","message":"{\"code\":\"noobaa_started\",\"entity_type\":\"NODE\",\"event_type\":\"STATE_CHANGE\",\"message\":\"Noobaa started\",\"scope\":\"NODE\",\"severity\":\"INFO\",\"state\":\"HEALTHY\",\"pid\":3379876}","host":"scale-13","severity":"notice","facility":"local2","syslog-tag":"node[3379876]:","source":"node"}
romayalon
nimrod-becker
Environment info
Platform: Kubernetes 1.14.1 | minikube 1.1.1 | OpenShift 4.1 | other: specify
rpm -qa |grep noobaa noobaa-core-5.15.0-20240115.el9.x86_64
Actual behavior
1.
you can observe that the nodes has the noobaa_nsfs restarts
[root@scale-13 log]# systemctl status noobaa_nsfs ● noobaa_nsfs.service - The NooBaa nsfs service. Loaded: loaded (/etc/systemd/system/noobaa_nsfs.service; enabled; preset: disabled) Active: active (running) since Thu 2024-01-18 11:11:30 CET; 56min ago Main PID: 3379876 (node) Tasks: 11 (limit: 48877) Memory: 134.2M CPU: 12.131s CGroup: /system.slice/noobaa_nsfs.service └─3379876 /usr/local/noobaa-core/bin/node /usr/local/noobaa-core/src/cmd/nsfs.js
/var/log/noobaa.log
other protocol node [root@scale-11 log]# systemctl status noobaa_nsfs ● noobaa_nsfs.service - The NooBaa nsfs service. Loaded: loaded (/etc/systemd/system/noobaa_nsfs.service; enabled; preset: disabled) Active: active (running) since Thu 2024-01-18 11:11:30 CET; 1h 11min ago Main PID: 494409 (node) Tasks: 11 (limit: 48877) Memory: 196.5M CPU: 24.462s CGroup: /system.slice/noobaa_nsfs.service └─494409 /usr/local/noobaa-core/bin/node /usr/local/noobaa-core/src/cmd/nsfs.js
where as below one didn't run into this postgres (panic message)
[root@scale-12 ~]# systemctl status noobaa_nsfs ● noobaa_nsfs.service - The NooBaa nsfs service. Loaded: loaded (/etc/systemd/system/noobaa_nsfs.service; enabled; preset: disabled) Active: active (running) since Thu 2024-01-18 08:48:16 CET; 3h 34min ago Main PID: 3996087 (node) Tasks: 11 (limit: 48877) Memory: 98.0M CPU: 53.449s CGroup: /system.slice/noobaa_nsfs.service └─3996087 /usr/local/noobaa-core/bin/node /usr/local/noobaa-core/src/cmd/nsfs.js
I didn't do any operations or max it could be due to not setting the region it failed ?
Expected behavior
Steps to reproduce
More information - Screenshots / Logs / Other output