Troubleshooting

You can run SocketMan in the foreground in order to troubleshoot different issues. Before you run it in the foreground, make sure it has been stopped.

/etc/init.d/socketman stop

After this, you can start it in the foreground

/usr/bin/socketman --config=/etc/socketman

Scripts, configs, ssh password, etc not arriving on the AP

Make sure the device profile is added to https://github.com/mylittletony/SocketMan/blob/master/boards.yml

0 Message

DEBUG http.c:277: Initializing against https://api.ctapp.io/api/v2/init
DEBUG http.c:315: Could not initialize, device not found (0).
DEBUG http.c:277: Initializing against https://api.ctapp.io/api/v2/init
DEBUG http.c:315: Could not initialize, device not found (0).

1. You do not have a working internet connection. This might be due to the missing WAN interface or the cable not being plugged in.

404 Message

DEBUG http.c:277: Initializing against https://api.ctapp.io/api/v2/init
DEBUG http.c:315: Could not initialize, device not found (404).
DEBUG http.c:277: Initializing against https://api.ctapp.io/api/v2/init
DEBUG http.c:315: Could not initialize, device not found (404).

1. If this device was previously initialized, you will need to reset it from your dashboard.
2. Check that the right MAC address is added to your location.
3. Check your Location Security Settings - http://docs.cucumberwifi.io/article/454-device-security-levels/

If in doubt, reset the device from the dashboard!

Data could not be sent (0)

Stats collection finished in 0.03505 seconds
DEBUG cache.c:20: Caching the datas!
DEBUG http.c:228: Data could not be sent (0)

1. Check your internet connection.
2. Make sure you have libcurl 7.53.1 installed. In 7.52.1 there is a known bug which prevents SM cached data from beeing sent.

• If you can't upgrade to the latest curl version, add "no-cache": 1 to /etc/socketman so that your config looks similar to this

{
        "username": "AAAAAAAAAAA",
        "password": "AAAAAAAAAAA",
        "topic": "tpc_fhbiAQcWmBhlVFqDdRHiKOmFOixoyWtxgrqptTvCPyQTedWW",
        "key": "key_ALCCoCEXoPZABTGDDDDKySCZwLK",
        "api_url": "https://api.puffin.ly/v1",
        "stats_url": "https://api.ctapp.io/api/v2/collector",
        "mac": "AA-DE-11-44-22-AA",
        "mqtt_host": "sync.puffin.ly",
        "token": "pubt_aaabbbwyVdcfOLLdyQQQTFFFfrfpuO",
        "port": 443,
        "monitor": 15,
        "sleep": 60,
        "tls": true,
        "cacrt": "/etc/cacrt.pem",
        "debug": false,
        "scan": 1,
        "survey": 0,
        "no-cache": 1
}

• There is no way to do this from CT, so that config might get overwritten by CT if you reset it.
• That config will get send by CT, and you cannot get it in any other way.

Error opening file!

DEBUG http.c:319: Device found, extracting configs.........
Error opening file!

1. Make sure you have selected the correct config location /etc/socketman, and not a directory