OPNsense Forum

Archive => 21.1 Legacy Series => Topic started by: annoniempjuh on July 28, 2021, 11:43:11 am

Title: 21.1.9 update weardnes
Post by: annoniempjuh on July 28, 2021, 11:43:11 am

yesterday i updated OPNsense to 21.1.9 and today i found out that Sensei stopped working (SWAG usage was to hight) checked the logbook and found the following errors:

Code: [Select]

2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:
2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:
2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:
2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:
2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:
2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:
2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:
2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:
2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:
2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:
2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:
2021-07-27T18:08:11 configctl[49709] event @ 1627401591.49 msg:

Code: [Select]

2021-07-27T18:37:00 kernel swap_pager_getswapspace(18): failed
2021-07-27T18:37:00 kernel swap_pager_getswapspace(24): failed
2021-07-27T18:37:00 kernel swap_pager_getswapspace(32): failed
2021-07-27T18:37:00 kernel swap_pager_getswapspace(18): failed
2021-07-27T18:37:00 kernel swap_pager_getswapspace(24): failed
2021-07-27T18:37:00 kernel swap_pager_getswapspace(32): failed
2021-07-27T18:37:00 kernel swap_pager_getswapspace(18): failed
2021-07-27T18:37:00 kernel swap_pager_getswapspace(24): failed
2021-07-27T18:37:00 kernel swap_pager_getswapspace(32): failed
2021-07-27T18:37:00 kernel swap_pager_getswapspace(24): failed
2021-07-27T18:37:00 kernel swap_pager_getswapspace(32): failed
Rebooted OPNsense and the syslog got spammed with this error:

Code: [Select]

2021-07-28T11:32:00 api[78935] [2021-07-28T11:32:00+02:00][error] no active session, user not found
2021-07-28T11:31:59 api[31981] [2021-07-28T11:31:59+02:00][error] no active session, user not found
2021-07-28T11:31:58 api[62532] [2021-07-28T11:31:58+02:00][error] no active session, user not found
2021-07-28T11:31:56 api[31981] [2021-07-28T11:31:56+02:00][error] no active session, user not found
2021-07-28T11:31:55 api[71330] [2021-07-28T11:31:55+02:00][error] no active session, user not found
2021-07-28T11:31:54 api[62532] [2021-07-28T11:31:54+02:00][error] no active session, user not found
2021-07-28T11:31:53 api[31981] [2021-07-28T11:31:53+02:00][error] no active session, user not found
2021-07-28T11:31:51 api[50564] [2021-07-28T11:31:51+02:00][error] no active session, user not found
2021-07-28T11:31:50 api[62532] [2021-07-28T11:31:50+02:00][error] no active session, user not found
2021-07-28T11:31:49 api[31981] [2021-07-28T11:31:49+02:00][error] no active session, user not found
2021-07-28T11:31:48 api[50564] [2021-07-28T11:31:48+02:00][error] no active session, user not found
2021-07-28T11:31:46 api[62532] [2021-07-28T11:31:46+02:00][error] no active session, user not found
2021-07-28T11:31:45 api[31981] [2021-07-28T11:31:45+02:00][error] no active session, user not found
2021-07-28T11:31:44 api[50564] [2021-07-28T11:31:44+02:00][error] no active session, user not found
2021-07-28T11:31:43 api[62532] [2021-07-28T11:31:43+02:00][error] no active session, user not found
note; i updated at 2021-07-27T11:29:49, but the logbook don't have any syslogs before 2021-07-27T18:08:11 ???

now 10 minutes later, no more spamming the logbook, and it looks like everything is working normally.
going to monitor this and will report later this day if there is something else...

Title: Re: 21.1.9 update weardnes
Post by: fhloston on July 28, 2021, 01:31:47 pm

seing the same on multiple installations.

seems configd from before the upgrade to 21.1.9 is stuck:

Code: [Select]

45073  -  R      507:46.32 /usr/local/bin/python3 /usr/local/opnsense/service/configd_ctl.py -e -t 0.5 system even
after reboot it's gone.

Code: [Select]

service configd restart does not stop the old process.

Title: Re: 21.1.9 update weardnes
Post by: mimugmail on July 28, 2021, 04:38:23 pm

Api error comes cause session is gone due to reboot but browser still open, nothing to worry.