-
-
Notifications
You must be signed in to change notification settings - Fork 610
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 connect hddtemp host #57
Comments
Usually it helps to see whether conky mentions anything relevant on stderr (i.e. run it in a terminal and see what it says). I believe using netcat would pretty much do the same thing conky does, so can you see if |
I did run it from terminal, and it reports what I said in the thread title, sorry for not specifying it. After running: Netcat gave me the temperature and model name of the first HDD, but when I would do: |
I don't think |
Nope, strangely hddtemp does not pop up, the configuration file is set for hddtemp to run as a daemon, even tried to do |
Check that hddtemp is still running. In the latest Debian, it sometimes shuts down itsel (confirmed bug), thus Conky can't access it. |
vi /etc/default/hddtemp hddtemp network daemon switch. If set to true, hddtemp will listen for incoming connections.set RUN_DAEMON="false" => RUN_DAEMON="true" then 'service hddtemp restart/start' |
Chalking this up as an odd case and move on. Also, |
I've had conky work properly with hddtemp before I reinstalled the OS (CrunchBang with Debian testing repos), and this time it doesn't work at all, even with the same settings.
I've tried with the default interface and port, also specifying custom values for those two (and I changed that in the conky config file too), made sure that I have the right permissions on /usr/sbin/hddtemp (I can see the temp values without any root privileges or a sudoer), and made sure that the daemon is running.
Here's the relevant part of conky:
HDD1:${alignr}${hddtemp /dev/sdb}°C
HDD2:${alignr}${hddtemp /dev/sda}°C
Any help would be appreciated
The text was updated successfully, but these errors were encountered: