*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
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.
Hi my machine is a FreeBSD system so not Linux per se but I thought I'd ask for help here anyway as I am in a panic. My system keeps rebooting. It comes up, goes through its sequence and then reboots again. It comes up on the network. I can ssh into it and then after about 20 minutes I'm kicked off again as it reboots again.
Hi my machine is a FreeBSD system so not Linux per se but I thought I'd ask for help here anyway as I am in a panic. My system keeps rebooting. It comes up, goes through its sequence and then reboots again. It comes up on the network. I can ssh into it and then after about 20 minutes I'm kicked off again as it reboots again.
Any help would be greatly appreciated.
Without any sort of details, there is nothing much we can help with. If you can get in for 20 minutes, then download the log files as quickly as you can, and see what they say. There has to be SOME sort of hint as to what's going on...if not, you may be having a hardware problem. But again, without details, we can't even guess.
Is it a software problem or hardware one? Without allowing to boot straight to freebsd, can you pause the boot process; example getting into bios screen or hanging in boot loader screen. Wait for 20 or 60 minutes.
What I am trying to say is isolate the problem one by one. First determine if it is a particular OS problem,if can't be determined goto a level deeper by seeing system functioning with just BIOS loaded. Or not because of a corrupted BIOS. Then it may be regarded as hardware problem.
If it's a hardware problem then a malfunctioning reboot or power switch, loose memory card, interface connectors, overheating cpu, non running cpu fan coolers, mulfunctioning power supply, loose power cords and etc.
Strangely it has stopped rebooting. The problem seems to be however that IP addresses are not getting assigned to the interfaces at reboot.
They are set in the rc.conf file but when the machine reboots none of the vlans have an IP address. I notice in the rc.conf file that route definnitions
are added before the ifconfig commands. Would that make any difference?
Thanks guys,
Strangely it has stopped rebooting. The problem seems to be however that IP addresses are not getting assigned to the interfaces at reboot.
They are set in the rc.conf file but when the machine reboots none of the vlans have an IP address. I notice in the rc.conf file that route definnitions
are added before the ifconfig commands. Would that make any difference?
Yes, since if the interfaces aren't configured, the routes can't be added, since the system doesn't know anything about any networks at that point.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.