We have a system that works as follows:
Bluetooth scanners report data to Bluetooth access points. The Bluetooth access points are networked to a small computer that runs some sort of small version of Linux (Edit: QNX) that fits on a CF card. This computer then reports the scanned data to a server and from there the information is further distributed.
The server resets at the same time every day. Most of the time this does not cause an issue, however about once a week the small Linux computer will quit transmitting data to the server after the server reset. The data is still there and it retransmits after the small Linux computer is rebooted.
We looked into this was if it were a network issue but both systems ping just fine.
The issue seems to be with the "spooler", which evidently puts itself on pause (some of the time) after a break in communication.
I think the spooler is just a standard Linux (Edit: QNX) feature so I'm hoping someone will know a bit about it.
This is out of some log file, I don't understand it so I don't even know if it is relevant.
spooler -d /dev/null -c /etc/printers/ps.cfg -nlpt1 &
I've been reading about the dev/null which seems like it is just a bit bucket, not the actual was this thing transmits data??
Anyhow is there some way to make the spooler recheck the network and start transmitting data again automatically?
I might be able to get more specific details if they are required for troubleshooting.
Bluetooth scanners report data to Bluetooth access points. The Bluetooth access points are networked to a small computer that runs some sort of small version of Linux (Edit: QNX) that fits on a CF card. This computer then reports the scanned data to a server and from there the information is further distributed.
The server resets at the same time every day. Most of the time this does not cause an issue, however about once a week the small Linux computer will quit transmitting data to the server after the server reset. The data is still there and it retransmits after the small Linux computer is rebooted.
We looked into this was if it were a network issue but both systems ping just fine.
The issue seems to be with the "spooler", which evidently puts itself on pause (some of the time) after a break in communication.
I think the spooler is just a standard Linux (Edit: QNX) feature so I'm hoping someone will know a bit about it.
This is out of some log file, I don't understand it so I don't even know if it is relevant.
spooler -d /dev/null -c /etc/printers/ps.cfg -nlpt1 &
I've been reading about the dev/null which seems like it is just a bit bucket, not the actual was this thing transmits data??
Anyhow is there some way to make the spooler recheck the network and start transmitting data again automatically?
I might be able to get more specific details if they are required for troubleshooting.
Last edited:
Facebook
Twitter