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

Could not initialize class bad.robot.temperature.IpAddress$ #113

Open
AdnamsDeveloper opened this issue Jul 26, 2023 · 0 comments
Open

Could not initialize class bad.robot.temperature.IpAddress$ #113

AdnamsDeveloper opened this issue Jul 26, 2023 · 0 comments

Comments

@AdnamsDeveloper
Copy link

Hello, we have temperature-machine installed on three Raspberry Pi 4 Model B Rev 1.5s, two as clients and one as the server.

I am intermittently getting the following error in the temperature-machine.log file:

2023-07-26 09:02:51:223+0100 [temperature-reading-thread-1] ERROR An error occurred executed a scheduled task (RecordTemperature(bad.robot.temperature.ds18b20.SensorReader@1363df7,HttpUpload(temp-wareh/127.0.0.1,Client(Kleisli(org.http4s.client.blaze.BlazeClient$$$Lambda$732/20340783@e93c),IO$16419391)),bad.robot.temperature:DEBUG in 4c12b6)) Could not initialize class bad.robot.temperature.IpAddress$

The device is reachable over the network, it's connected via wifi and ifconfig shows the following:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.7.22 netmask 255.255.255.0 broadcast 192.168.7.255 inet6 fe80::39bc:cfba:a738:420d prefixlen 64 scopeid 0x20<link> ether e4:5f:01:cb:0c:ce txqueuelen 1000 (Ethernet) RX packets 2528350 bytes 658068666 (627.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1269346 bytes 205970892 (196.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I understand that this could be related to the content of the hosts file, so here is the contents of that:

pi@temp-wareh:~ $ more /etc/hosts 127.0.0.1 temp-wareh

The symptoms seem to vary, but right now when I browse to the server it shows the temperatures from the two clients, but not from itself. The hardware is fine as I can read the DS18B20 directly:

pi@temp-wareh:~ $ cat /sys/bus/w1/devices/28-062130a4e2a6/w1_slave e5 00 4b 46 7f ff 0c 10 ed : crc=ed YES e5 00 4b 46 7f ff 0c 10 ed t=14312

How can I troubleshoot this error, please? Thank you

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

1 participant