after a reboot of my Lenny system, the default gateway will lost. Then i must try "networking restart" and the gatway will be set
my interfaces looks :
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
[Code].....
Google brought me no love on this one, tried searching here with little luck as well. So I'm hoping somebody vastly more experienced than I can shed some light on my plight.
The situation:
I have a CentOS 5.3 x64 server running the latest cPanel which works fantastic. I issued a graceful reboot and the server came back up (according to the DC) just fine to a login prompt. Apparently the system lost all of its IP address configuration. Primary IP, secondary IP's gateway, you name it and it was gone. Now my secondary IP's were showing in cPanel after I had the DC re-enter my main IP address/gateway. But listed as not active due to the fact that they were not anywhere to be attached to the interface. i.e. eth0:1 eth0:2 etc and so on.
I have no idea where to begin looking for this problem and am afraid to reboot it again (at least until I get my lantronix spider up there). I've never experienced this with any of my other CentOS/cPanel servers either. All similar configurations CentOS 5.3 x64, latest cPanel as well. My hardware is all Supermicro gear as well and has been solid in the past.
Maybe I'm just missing something, granted I've only been managing Linux based servers for about two years now. This is actually the first real problem I've ran into on any Linux distro, they are normally pretty solid. So I assume it's a configuration error on my part somewhere.
I recently switched from Ubuntu server to Debian server, and I carried over many of the same configurations. This is pretty much a fresh install.
I cannot get the default gateway to stick by using the /etc/network/interfaces. I can ping my default gateway but nothing beyond it either by name or IP. code...
I would like the default gateway to stick between reboots. Could someone point me in the right direction?
I am *finally* getting around to rebuilding my file-sharing computer. I'll be sharing files with both Linux and Windoze machines. It's a home network, so there's nothing fancy needed. I know I have to tweak my smb.conf file until I'm satisfied with the features and security. I'm using SWAT and I'm starting with a bare-bones conf file. It's not secure but I can see the server and selected files/directories from my other Linux box.
My really dumb question is, do I have to reboot both the server and the client machines every time I change the SAMBA configuration? I thought I just had to stop and restart the SAMBA service in the SWAT software - but then the server disappears from my client. It looks like I need to reboot both machines for the client to see the server.
I insert the domain name "g3c" in menu: System->Administration->Network (file attach)
When i reboot the computer this information lost: why ?
Where i must insert this information ?
My s.o. is debian 5.05
I have a Bubba Two headless PC box and on it a Debian GNU/Linux Squeeze operating system.
I have upgraded my Bubba Two [URL]to Debian Squeeze from Debian Etch following these steps: Running Debian lenny or squeeze on Bubba Two [URL]
After this upgrade I have setup networking on Bubba following these steps: Setting up networking [URL]
In the case [URL] doesn't work, here are these steps:
[Code].....
I was running 2.6.26 and I've recently upgraded to 2.6.32-trunk-amd64 along with other packages (mostly dependencies)... which possibly involved the network stack.
After this upgrade my home gateway stopped working and I'm clueless to where the problem may be.
I can see that the iptables are still there when I type:
iptables -t filter -L -v -n -x --line-numbers
iptables -t nat -L -v -n -x --line-numbers
I have been trying to get my wireless interface work but i am unable to find a driver for the wireless interface.
View 1 Replies View RelatedA week ago I opened this thread viewtopic.php?f=17&t=61580 in "Board index ‹ Help ‹ Installation" and asked for a moderator to move this to here. Because it hasnt happened up to know, I am reopening the thread here. It would be reeeeally great if somebody could help me with my problem!
I own two computers, one netbook and one laptop. I want to boot my netbook as a diskless client via PXE.I set up a dhcp-, tftp and nfs-server on my laptop but when i boot my netbook, the follwoing messages are displayed:(to make it more clear, i uploaded the whole output and shortened the output below)
[Code]...
Some problems keep bothering me and dont let me use my debian sqeeze with joy.Im in network with no DHCP on. When installing i didnt configure my eth network card.After each restart i need to configure manually my eth because it loses it.
View 7 Replies View RelatedDebian Testing, updated daily, running Gnome.
A week ago, a new router was installed at the office and now my system "loses" the networks printers and forces me to manually select them within Cups various times a day to be able to print. The issue was not present when the old router was in place, and all my colleagues can print without problems using their Windows machines.
This only affects printing, for Simple Scan can always communicate with the printers without problems.
The printers are two basic Epson L355 (those with ink tanks) and the "official" driver (from Open Printing) has been working perfectly since I installed Debian. The whole Cups and Avahi stack is installed, and I even added system-config-printer this week to make sure that I was not missing a package.
Because the only variable that changed is the router, there has to be something there messing with my Cups or Avahi configuration.
Note that the new router had a "vanilla" installation, where no advanced settings were touched. All connected devices (computers, mobile phones, printers, etc.) are given new IP address through DHCP every day.
Where should I start? I have already deleted and added the printers within Cups several times during the week, and the problem persists. Is the router renewing the address more often than the old one did? Can this "refresh" be delayed? Should Avahi monitor devices more often?
I guess that I could configure the router and give static IP addresses to the printers, but such a setting was not present in the old router and my computer could locate the printers without problems.
I recently purchased a Wacom Bamboo CTH-460 and have had endless frustration trying to get it to work.
I started by getting the latest stable source from the Linux Wacom project and trying to compile the drivers and kernel modules from source and installing them, though nothing ever seemed to work. If I do lsmod it shows that the wacom kernel module is loaded but when I do more /proc/bus/usb/devices I end up with this:
And no matter what I try it always says Driver=(none). So that means none of the /dev/input events are getting any data from the tablet, which means there's no way for it to do anything with X. So that is the step I am stuck at.
After some time I came to suspect that perhaps the CTH-460 is too new to be supported, and am now trying to compile drivers from the lastest development source realeased on 12-30-09. It said there was support for 5 new Bamboo tablets. However when I try to make the driver I run into this error:
I'm not sure if that is just an error in the make script or not, and if it is, why no one else has said anything about it.
Maybe I'm going about this all wrong, do I even need a new kernel driver for my tablet model? Do I only need an Xorg driver? What modules and drivers need to be in place before I should at least get the tablet tied to an input event?
I have recently installed debian on to a system that I built as a media server. It has 4 1TB HDDs in the machine and each drive was partitions as follows:
10 MB /boot -md0
1 GB swap -md1
remaining / -md2
I had the /boot running as a raid 1 so i could make backups and the swap was running raid 0 for 4 GB of swap striped. The rest was all setup as a raid 5.I setup the system using mdadm and all worked out perfect. The system worked fine on reboot and all the raids showed no degration on them. However when the debian update icon came up on the screen came up I opened it and it said I needed some updates which was fine. So it did the updates to my system. system was still fine.
I rebooted my vServer (Debian 8) and it doesn't came back up. Well, I used the rescue console on my server and the server seems to be running fine, except the network was broken. So I tried 'ifconfig' but nothing came up. So I tried to enable my interface with 'ifconfig venet0 up', and now it appears in my ifconfig list
Code: Select allroot@i67svof:/var/www# ifconfig
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:557 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:36463 (35.6 KiB) TX bytes:0 (0.0 B)
My HWaddr doesn't look that well :) 'ip addr' prints this result:
Code: Select allroot@i67svof:/var/www# ip addr
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
These are the last lines in /var/log/syslog:
Code: Select allroot@i67svof:/var/www# tail /var/log/syslog
Feb 20 11:34:16 i67svof systemd[1]: Stopping memcached daemon...
Feb 20 11:34:16 i67svof systemd[1]: Stopping Network Name Resolution...
Feb 20 11:34:16 i67svof systemd[1]: Stopping Regular background program processing daemon...
Feb 20 11:34:16 i67svof systemd[1]: Stopping Login Prompts.
[Code] .....
And finally my network config in /etc/network/interfaces
Code: Select all# Auto generated lo interface
auto lo
iface lo inet loopback
# Auto generated venet0 interface
auto venet0
[Code] .....
Is it mandatory to reboot a public server after upgrading openssl? Or is it sufficient to restart the services?
View 2 Replies View RelatedIf I reboot my machine, the interface is down. How do I set the interface so it will start after I rebooted the machine?How do I do it in Debian?
View 3 Replies View RelatedI have installed Firestarter, and set it up following some manual (just a simple, baseline setting, nothing fancy). However, after restart I got error message: Starting the Firestarter firewall... failed! and then, later: startpar: service(s) returned failure: firestarter ... failed! Why this happens?
View 4 Replies View Relatedrecently i have combined 2 machines into 1. after doing this, the ping to the new machine stops, for no apparent reason, and consequently all traffic to/from the machine also stops. when using the two machines individually this never happened.Lastly, if i restart the network, it kills everything (like the network just wont restart - it reaches the last interface and hangs), and if i reboot the machine, it seems to be fine for about 3-4hours.has anyone seen anything like this when connecting a large number of hosts to 1 gateway, using linux as the router?
View 2 Replies View RelatedWhen I make a vpn connection to an openvpn server, I loose the internet connection.
The VPN works all right.
Server config (extract)
Client config
Client route without the VPN connection
client route with VPN connected (internet lost)
Is there anything I can do to the push rule of the servers's config file?
Upgraded webserver to Jessie as an upgrade to Wheezy produced errors, and before reboot everything was up and running, but as all upgrade docs and info I read, I rebooted the server. However it never came back. I have the original backup files before I did the Wheezy upgrade. I also have access by Rescue to the server.Made a back up of critical files and have a 24GB tar file and I can connect by SFTP.
how to check the Debian files... Grub etc.. I would prefer to find the issue than start again.I am not able to sudo from Putty. I cannot run apt-get update. I did go to chroot, but then I get unable to resolve host errors and Could not open lock file because Permission denied errors and asking if I am root.There is information by googling for start up issues, but as I am working remotely with a Rescue set up, a lot of the commands I see and have tied do not work.
A couple of days ago I asked why my pc changes the wireless card name.It switches between AR9285 ( right) and AR5008 ( wrong). Well, it is not the case. When system identified with AR9285,it loads ath9k and I can connect to the router. When system identifies my card as AR5008, no kernel module is present at all ( lspci -k). The wrong card name occurs only when system rebooted. If I gracefully shut down the system, it always comes up with a right name for the card( AR9285). So, how to force the system identify my card right no matter if I reboot or shut down?
View 1 Replies View RelatedHad an issue on one of my Debian stable servers the other day. After doing apt-get upgrade I was prompted to do autotoremove.
It wanted to autotremove
Code: Select allStart-Date: 2015-12-21 16:25:05
Commandline: apt-get autoremove
Remove: sendmail-cf:amd64 (8.14.4-8), exim4-config:amd64 (4.84-8), sendmail-base:amd64 (8.14.4-8)
End-Date: 2015-12-21 16:25:07
After doing this I rebooted my server (a few days later). After rebooting I had no ipv4. I tried statically assigning IP addresses to no avail. Ran ifconfig eth0 down/up which got me nowhere. Eventually decided to ask "Okay, what changed". Started installing packages that were autoremoved. Had to install from the apt cache using dpkg. First one I tried was sendmail-base. Then did ifconfig eth0 down/up, which gave me networking back.
I have checked the dependencies for sendmail-base and I see nothing that would relate to networking, so I'm really confused on why this happened. I had backups of the server so I went a week back and noticed sendmail-base was installed at that time. So I went a day back, where sendmail-base wasn't installed, and installed it. Sure enough it brought back networking. I'm just stating this because it is more proof that sendmail-base was the missing component.
I have lost my password for my root and for my user account.
Code: Select alluser@debian:~$ su
Password:
su: Authentication failure
user@debian:~$ su
Password:
su: Authentication failure
user@debian:~$ su
I have just installed a gust debian 8 on debian 8 host in virtualbox, and when i wonted too login as su/root on the host there where no login possible, is there a way to regain the root password for the host?
accidently deleated ubuntu lucid default theme,and lost the default user logon,it's now flat and gray.how to get it back?i still have the background, not the user logon
View 8 Replies View RelatedI've an Blade 1500, sparc64 IIIi with 2 hard disks and 2go of RAM. The computer run with debian 7.7.0 and BSD (opensxce) for each hard disks.
1/ When it's run under BSD there are no problems, the uptime are on many hours.
2/ when it's run under debian with XFCE x-window, the uptime is 4 hours 30 minutes and computer reboot automatically !
Into the control panel i've deactivate the hibernation, screensaver and power management ! I want to find the files for manage the time down. I think that the problem is in XFCE window manager.
I've upgraded a server on our LAN from fully functioning Wheezy to Jessie. All seems fine except remote administering using Putty from my windows workstation when issuing reboot from command line, it goes down and reboots but stops at login prompt asking for username and password and does not come back on the LAN network. This server does not normally have a monitor or keyboard so my ability to remote admin this server in effect is disabled.
If I log on, it will come back on the LAN network. I've checked the logs but can't see any errors. Is it in the configuration of Jessie somewhere or perhaps a Grub issue. I have 5 other production Wheezy servers that I intend to update to Jessie once I understand how to deal with this problem.
I'm getting weird behaviour while setting up an mdadm RAID1 array on debian 8.2.
After I set-up the array, lsblk shows:
Code: Select allsimon@debian-server:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
`-sda1 8:1 0 931.5G 0 part
`-md0 9:0 0 931.4G 0 raid1
sdb 8:16 0 931.5G 0 disk
[Code] ....
After a reboot, lsblk shows:
Code: Select allsimon@debian-server:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
`-sda1 8:1 0 931.5G 0 part
`-md0 9:0 0 931.4G 0 raid1
|-md0p1 259:0 0 811.6G 0 md
[Code] ...
I don't know where the md0p1 and md0p2 partitions are coming from. My /etc/fstab and /etc/mdadm/mdadm.conf both have nothing about this in them.
parted shows one partition on md0:
Code: Select allsimon@debian-server:~$ sudo parted /dev/md0 print
Model: Linux Software RAID Array (md)
Disk /dev/md0: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags:
Number Start End Size File system Flags
1 0.00B 1000GB 1000GB ntfs
Where the md0p1 and md0p2 partitions are coming from?
I'm setting up the array by doing as follows:
Delete existing device (I've done this a few times):
Code: Select allsudo mdadm --stop /dev/md0
sudo mdadm --remove /dev/md0
Zero drives:
Code: Select allsudo dd if=/dev/zero of=/dev/sda bs=1M count=1024
sudo dd if=/dev/zero of=/dev/sdb bs=1M count=1024
Create partition tables:
Code: Select allsudo parted /dev/sda mklabel gpt
sudo parted /dev/sdb mklabel gpt
Create full-disk partitions:
Code: Select allsudo parted -a optimal /dev/sda mkpart primary '0%' '100%'
sudo parted -a optimal /dev/sdb mkpart primary '0%' '100%'
Set raid flag on partitions:
Code: Select allsudo parted /dev/sda set 1 raid on
sudo parted /dev/sdb set 1 raid on
Create RAID array:
Code: Select allsudo mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[ab]1
Add filesystem (I'm using NTFS, but the problem also happens with ext4)
Code: Select allsudo mkfs.ntfs -f /dev/md0
I've been using various distros of Linux for over 20 years - but I'm stumped.
Was running Mint. But after taking an update a few weeks ago the network stopped working. After a lot of time and effort decided to give up on Mint and switch distros to Debian 8 Jessie.
But after changing the Network settings from default DHCP to my usual IPV4 static 10.net configuration and rebooting the network will not work.
I have several systems on a 10.100.0.0/16 LAN behind another Linux system acting as firewall/gateway.
Now, after about 7 hours of mining the Internet, I still can't get basic networking to work:
- Have tried a few combinations, with and without Network Manager and eth0 in interfaces
- /etc/network/interfaces is configured with a static IP and relevant parameters
- ifconfig shows eth0 and the correct information
- netstat -rn shows the basic default route to the gateway
- have tried with IPV6 enabled and disabled; it is not used on my LAN
The box is a desktop system, ASUS Maximum VI Formula mobo with onboard Ethernet, dual GTX 780 cards. Nothing very weird.
It all LOOKS right, but ping can't get off the box "destination unreachable", and no other system on the LAN can ping it.
I'm amazed a basic static IPV4 network setup completely breaks it. This is my main workstation - a dual-boot system where Windows runs fine - so it's not hardware.
EDIT: This has been solved. See the solution post: [URL]
A few days ago on my rss reader, I have read article about Ksplice uptrack that check updates for kernel and update kernel without reboot!
View 1 Replies View RelatedI have recently come across a Debian installation page for powerpc: viewtopic.php?t=20481. It got me motivated to fix the Debian I have on my iBook G4. I have a Debian Lenny installed on my iBook G4 -- but I have been having some sort of problem (mostly likely due to hardware) which causes the system to crash. After the latest crash, the clock on iBook has been readjusted. For this reason, I cannot reboot Debian completely.
Every time I turn on the computer it begins the booting process but before I get to my desktop I encounter numerous error messages concerning my clock. After either OK'ing or canceling these error messages, I get to my desktop but the system by then is either frozen or else not working at all. Worse, I can't even turn off the computer since the upper right corner of the desktop is completely blank and I have no menu to turn off or reboot the system.
It took this computer to a local Apple store and they ran many different hardware diagnostic tests on it. They concluded there's "technically" nothing wrong with the computer. But they said although the system has successfully passed all hardware tests, there may still remain some complicated but slight hardware glitch/es which the hardware diagnostics could not pick up.
