Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Location: /home/chenxiaolong and /root and /Users/chenxiaolong and C:\Users\chenxiaolong
Distribution: Fedora 12, Debian 5, Ubuntu 10.04
Posts: 17
Rep:
I know this thread is very old, but I'll still post a solution because it's still a problem in Fedora. There's actually a very easy fix:
1. Stop the tuncfg process: su -c 'killall tuncfg' OR sudo killall tuncfg
2. Log on to the root terminal: su -
3. Start tuncfg: tuncfg
4. Create the Hamachi config for the ROOT user: hamachi-init
5. Exit out of the root terminal: exit
6. Create the Hamachi config for the CURRENT user if you haven't already: hamachi-init
7. Use Hamachi!!
If you want to make tuncfg run automatically as root on boot up, then add it to /etc/rc.local: echo "tuncfg" | su -c 'tee -a /etc/rc.local' OR echo "tuncfg" | sudo tee -a /etc/rc.local.
Everything was going fine with the install until I got to the part where I run hamachi-init. It is nowhere to be find on my computer after running the installation process.
Got it!
This is indeed a very old thread but it's still the first hit when you try to google hamachi login failed (i.e. the terminal output)
So, I was trying all I could think of, tap/tun was enabled, tuncfg was running, and Hamachi worked perfectly until last reboot, yet login kept failing
Had a look into /home/<user>/.hamachi and found a .lock file
renamed to .lock.back, tried again, and guess what?
login succeeded.
This may or may not be the problem that the first poster had, but as the thread is still 'alive' and never solved, I thoughht it was a good idea to add what fixed it for me:
if Hamachi suddenly starts failing to login for no apparent reason even tho it did work before, remove or rename the file /home/<user>/.hamachi/.lock
well...
Turns out that simply removing the .lock file doesnt really do the trick. To make it work I have to use hamachi-init -f (force using the directory ~/.hamachi even tho it already exists).
Doing that and then removing the lock usually gets me back on line, but with 2 small problems:
- a new Hamachi IP every time. Kind of a PITA (I have to change a number of scripts)
- all this dang thing has to be done every time I reboot my Linux server. It doesnt happen all that often but still...
Im trying to find out why this happens so I can try to really fix it. None of the hints in this thread helped so far, except from my dirty workaround (with new IP at every use )
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.