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 connect hddtemp host #57

Closed
andoruB opened this issue Jul 27, 2014 · 7 comments
Closed

Could not connect hddtemp host #57

andoruB opened this issue Jul 27, 2014 · 7 comments

Comments

@andoruB
Copy link

andoruB commented Jul 27, 2014

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

@Tucos
Copy link

Tucos commented Jul 27, 2014

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 nc 127.0.0.1 7634 yields some result?

@andoruB
Copy link
Author

andoruB commented Aug 1, 2014

I did run it from terminal, and it reports what I said in the thread title, sorry for not specifying it.
I tried to run netcat, and it gave me this:
(UNKNOWN) [127.0.0.1] 7634 (?) : Connection refused

After running:
$hddtemp -d /dev/sda

Netcat gave me the temperature and model name of the first HDD, but when I would do:
$hddtemp -d /dev/sdb
It would still show me details about the first HDD which is weird.
Doing
$ hddtemp /dev/sd[ab]
However will report the correct data on both HDDs, so there might be something wrong with the daemon. I've triple checked, the hddtemp config file is set to run as a daemon, permissions are set correctly, I tried to restart the daemon countless of times, but it still won't work.

@Tucos
Copy link

Tucos commented Aug 2, 2014

I don't think hddtemp /dev/sdb would talk to the daemon and I'm not sure
specifying a disk in combination with -d does what one would expect. So
just to be sure it's actually running as daemon and listening on the port,
does ss -tnlp (or netstat -tnlp if you don't have iproute2) show hddtemp? If
so, what address and port?

@andoruB
Copy link
Author

andoruB commented Aug 4, 2014

Nope, strangely hddtemp does not pop up, the configuration file is set for hddtemp to run as a daemon, even tried to do invoke-rc.d restart hddtemp after modifying the config file. I really have no idea why it's not working, but it's clear that it's not a conky issue.

@Ovnuniarchos
Copy link
Contributor

Check that hddtemp is still running. In the latest Debian, it sometimes shuts down itsel (confirmed bug), thus Conky can't access it.

@sparkyvxcx
Copy link

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"
:wq

then 'service hddtemp restart/start'
it works on my ubuntu 16.04 laptop

@lasers
Copy link
Contributor

lasers commented Aug 3, 2018

Chalking this up as an odd case and move on. Also, ${hddtemp /dev/sda} work okay for me.

@lasers lasers closed this as completed Aug 3, 2018
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

5 participants