Sfpswitch.py Error message

This Errormessage appears even after factory reset: what does it mean?

2016-10-16T10:21:42+02:00 debug updater[2334]: src/lib/journal.c:123 (journal_open): Opening journal
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: DEBUG:src/lib/journal.c:123 (journal_open):Opening journal
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: line not found
2016-10-16T10:21:42+02:00 debug updater[2334]: src/lib/interpreter.c:104 (interpreter_error_result):
Stack Traceback

(2) Lua function ‘?’ at line 64 of chunk '“logging”]'
Local variables:
err = string: "[string “transaction”]:325: No journal to recover"
err2string = Lua function ‘?’ (defined at line 45 of chunk “logging”])
msg = string: “
[string “transaction”]:325: No journal to recover”
(*temporary) = table: 0x1f04ec0 {msg:
[string “transaction”]:325: No journal to recover}
(3) C function ‘function: 0x1f03320’
(4) field C function ‘recover’
(5) Lua global ‘recover’ at line 325 of chunk '“transaction”]'
Local variables:
run_state = table: 0x1cb08d0 {initialized:true, init:function: 0x1cb0900, lfile:userdata: 0x1cff568, release:function: 0x1cddd20 (more…)}
(6) Lua function ‘?’ at line 386 of chunk '“transaction”]'
Local variables:
(*temporary) = Lua function ‘?’ (defined at line 352 of chunk “transaction”])
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: DEBUG:src/lib/interpreter.c:104 (interpreter_error_result):
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: Stack Traceback
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: ===============
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: (2) Lua function ‘?’ at line 64 of chunk '“logging”]'
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: Local variables:
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: err = string: "[string “transaction”]:325: No journal to recover"
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: err2string = Lua function ‘?’ (defined at line 45 of chunk “logging”])
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: msg = string: "
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: [string “transaction”]:325: No journal to recover"
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: (*temporary) = table: 0x1f04ec0 {msg:
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: [string “transaction”]:325: No journal to recover}
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: (3) C function 'function: 0x1f03320’
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: (4) field C function 'recover’
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: (5) Lua global ‘recover’ at line 325 of chunk '“transaction”]'
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: Local variables:
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: run_state = table: 0x1cb08d0 {initialized:true, init:function: 0x1cb0900, lfile:userdata: 0x1cff568, release:function: 0x1cddd20 (more…)}
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: (6) Lua function ‘?’ at line 386 of chunk '“transaction”]'
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: Local variables:
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: (*temporary) = Lua function ‘?’ (defined at line 352 of chunk “transaction”])
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]:
2016-10-16T10:21:42+02:00 crit updater[2334]: src/opkg-trans/main.c:95 (main):
[string “transaction”]:325: No journal to recover
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: DIE:src/opkg-trans/main.c:95 (main):
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: [string “transaction”]:325: No journal to recover
2016-10-16T10:21:42+02:00 emerg sfpswitch.py[1524]: Aborted

1 Like

Same here:

https://discourse.labs.nic.cz/t/fiber7-switzerland-sfp-compatibility/995/6?u=emeidi

QA fail.

These messages are actually cross-feeded from updater. And the message says, that updater journal recovery failed, meaning that there is nothing to recover, so no failed or interrupted update has been found.

The problem seems to be 1) in procd - it confuses updater STDERR output with sfpswitch output; 2) in updater that feeds its messages to syslog directly and to STDERR as well and 3) in sfpswitch that should use STDERR only when it is executed from console and syslog otherwise.

Currently you can ignore these startup messages. Moreover, you can kill a start sfpswitch.py from console with --nodaemon parameter to see the output directly. Most importantly, this does not have anything to do with the SFP module support issues, it just causes confusion.

1 Like