Help with Fresh Install of 1.11 on Raspberry Pi

[Sandy Matheson]

Hi,

Sadly my NCID that I installed on a CHIP 3 years ago has died and I’m now starting from scratch again. I’m using a Pi Zero W and installed the latest version of Raspbian - Raspbian GNU/Linux 10 (buster).

After installing Raspbian and updating it I installed gdebi using:
sudo apt-get install gdebi

I then installed the latest versions (1.11) of ncid and ncid-client

The first hurdle was the error:
/usr/bin/ncid: line 36: type: tclsh: not found
/usr/bin/ncid: line 38: type: wish: not found

This was resolved eventually by running:
sudo apt-get install tcl tk

The problem I now have is that when I run:
sudo update-rc.d ncidd defaults
I get the error:
update-rc.d: error: unable to read /etc/init.d/ncidd

When I list the files in /etc/init.d/ there are no entries for ncidd

Any ideas how to solve this?

Thanks for your help,

Sandy

[Ed Attfield]

The newest ncidd and raspbian are using systemd to start daemons, the instructions you show are for initd.

The latest install instructions are here

http://ncid.sourceforge.net/doc/NCID-UserManual.html#instl_deb_top

[Sandy Matheson]

Thank you - problem solved.

[Sandy Matheson]

OK - all was working yesterday. This morning I setup python and a script to link to IFTTT to trigger Pushover for notifications to my iPhone. Now NCID won't launch.

The ncidd.log file doesn't show any errors

Running systemctl shows
● ncid-notify.service loaded failed failed NCID using the NMA Output
● ncidd.service loaded failed failed Network Caller ID server

Running: sudo systemctl start ncidd - results in
Job for ncidd.service failed because the control process exited with error code.
See "systemctl status ncidd.service" and "journalctl -xe" for details.

Running: systemctl status ncidd.service - results in
● ncidd.service - Network Caller ID server
Loaded: loaded (/lib/systemd/system/ncidd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-12-28 10:34:14 GMT; 39s ago
Docs: man:ncidd(8)
Process: 508 ExecStart=/usr/sbin/ncidd --pidfile /run/ncidd.pid (code=exited, status=11)

Dec 28 10:34:14 callblocker3 systemd[1]: Starting Network Caller ID server...
Dec 28 10:34:14 callblocker3 systemd[1]: ncidd.service: Control process exited, code=exited, status=11/n/a
Dec 28 10:34:14 callblocker3 systemd[1]: ncidd.service: Failed with result 'exit-code'.
Dec 28 10:34:14 callblocker3 systemd[1]: Failed to start Network Caller ID server.

Running: journalctl -xe - last entry is
Dec 28 10:34:14 callblocker3 systemd[1]: Failed to start Network Caller ID server.
-- Subject: A start job for unit ncidd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit ncidd.service has finished with a failure.
--
-- The job identifier is 446 and the job result is failed.

[Ed Attfield]

If I'm reading the systemd output correctly, status=11 means ncidd has exited with SIGSEGV.

You can try starting ncidd on the command line with
sudo /usr/sbin/ncidd -Dv3

I expect that it will also exit promptly so that
echo $?
will give 11.

You may be seeing the known bug in 1.11 which affects the reading of ncidd.blacklist/whitelist/alias files. ncidd will segv sometimes when a line has only whitespace characters.

In 1.11, which makes it appear more often, I accidentally put a whitespace line in the starter ncidd.whitelist line 2, see

https://sourceforge.net/p/ncid/bugs/41/#0b9a

[Sandy Matheson]

Thank you. I've now removed and reinstalled NCID and it appears to be working OK. Fingers crossed!