Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

basicstation process interrupted on Kerlink Wirnet Station #53

Closed
istina-iot opened this issue Jan 17, 2020 · 3 comments
Closed

basicstation process interrupted on Kerlink Wirnet Station #53

istina-iot opened this issue Jan 17, 2020 · 3 comments

Comments

@istina-iot
Copy link

After short time, regularly, basicstation process interupted
Log:

2020-01-17 06:39:27.729 [TCE:INFO] MUXS reconnect backoff 1s (retry 0)
2020-01-17 06:39:28.745 [TCE:VERB] Connecting to MUXS...
2020-01-17 06:39:28.748 [TCE:VERB] Connected to MUXS.
2020-01-17 06:39:28.805 [any:CRIT] Radio device '/dev/spidev32766.0' in use by process: 1609

but ps | grep 1609 show nothing.

@istina-iot
Copy link
Author

This happens every time after the loss and restore connection with LNS:

2020-01-17 07:18:52.797 [AIO:DEBU] [4] Connection closed unexpectedly
2020-01-17 07:18:52.797 [AIO:DEBU] [4] WS connection shutdown...
2020-01-17 07:18:52.798 [TCE:VERB] Connection to MUXS closed in state 4
2020-01-17 07:18:52.799 [TCE:INFO] MUXS reconnect backoff 1s (retry 0)
2020-01-17 07:18:53.816 [TCE:VERB] Connecting to MUXS...
2020-01-17 07:18:53.818 [TCE:VERB] Connected to MUXS.
2020-01-17 07:18:53.874 [any:CRIT] Radio device '/dev/spidev32766.0' in use by process: 2539

@jawadiot
Copy link

I have the same error, any oneknow what cause this error ?

@beitler
Copy link
Contributor

beitler commented May 14, 2020

Thanks for reporting the issue. This is fixed in the upcoming release.
Until then, as a work around you could start station in daemon mode using flag -d (see station --help for more details). This will cause station to start in the background, and additionally it will fork into a child-process such that the parent remains the daemon control process which restarts the the child when it exits for some reason. In the log you will see something like:

2020-05-14 10:55:23.175 [any:CRIT] Radio device '/dev/spidev32766.0' in use by process: 17882
2020-05-14 10:55:23.596 [SYS:ERRO] DAEMON: Station process 17882 died (exit code 0x1E00)
2020-05-14 10:55:23.606 [SYS:INFO] DAEMON: Station process 17943 started...

In order to be able to inspect the log in daemon mode you should specify a log file inside station.conf, like this:

...
    "station_conf": {
        "log_file":  "/var/log/station.log",
        "log_level": "DEBUG",  /* XDEBUG,DEBUG,VERBOSE,INFO,NOTICE,WARNING,ERROR,CRITICAL */
        "log_size":  10000000,
        "log_rotate":  3,
         ...
    }
...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants