Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
my server tech support says it's all normal. go figure.
If the server rebooting all the time is normal, you should probably look for a different server.
But maybe they meant login from 127.0.0.1 is normal, in which case it seems they are correct: http://kb.odin.com/en/119663
Quote:
Question
I see several active admin sessions on localhost with address 127.0.0.1. Does it mean that somebody else is logged on Plesk server?
Answer
This is expected behavior. You can watch the active localhost admin sessions during daily maintenance script usually. The process runs as Plesk administrator ('psaadm' system user) and perform maintenance tasks.
You need to step back and take a deep breath... no humor intended.
No one is logging in from 127.0.0.1 - that address is not visible - at all - from the outside.
Many machine processes will use 127.0.0.1 for various purposes - but not for login.
But when people have asked for more info, just saying that it reboots due to a login to 127.0.0.1 is totally unhelpful and uninformative. On the other hand, you undoubtedly think that is the major cause of the problem.
So, could you explain a little more precisely, with some actual messages or log lines that lead you to that conclusion. Perhaps that will allow us to understand why you have reached that conclusion and lead to a resolution.
still just creepers.. (wankin off and laughin like little jerkoffs in the background..probably)
Frustrated you may be but still some of your language in this thread is not acceptable.
So I'm warning you (in a friendly way) you should mind both your tongue and attitude.
Thanks in advance.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.