Troubleshooting unexpected keyword argument 'logged_out'“ error
After upgrading, you may see an "unexpected keyword argument 'logged_out'" error. This article explains how to fix it.
LAST TESTED ON CHECKMK 2.3.0P1
Table of Contents
Problem
User is unable to activate changes on a Checkmk site due to an error of “init() got an unexpected keyword argument 'logged_out'.“
Solution
This error is caused by a "logged_out": False," flag enabled within the session_info.mk file of the automation user. That file will need to be deleted.
Delete the
session_info.mkfile located in~/var/check_mk/web/automation/directoryOMD[mysite]:~$ cd ~/var/check_mk/web/automation/ OMD[mysite]:~/var/check_mk/web/automation$ ls -l -rw-rw---- 1 mysite mysite 21 Jun 27 15:17 automation.secret -rw-rw---- 1 mysite mysite 573 Jun 27 15:17 cached_profile.mk -rw-rw---- 1 mysite mysite 2 Jun 27 15:17 enforce_pw_change.mk -rw-rw---- 1 mysite mysite 11 Jun 27 15:17 last_pw_change.mk -rw-rw---- 1 mysite mysite 2 Jun 27 15:17 num_failed_logins.mk -rw-rw---- 1 mysite mysite 2 Jun 27 15:17 serial.mk -rw-rw---- 1 mysite mysite 2 Jun 27 15:17 session_info.mk OMD[mysite]:~/var/check_mk/web/automation$ rm session_info.mk.
Restart the Checkmk site
OMD[mysite]:~$ omd restart.
Login and activate changes