Hi.  I'm still using 4.1 since it has been working without issue for many months...until now, of course!  It was fine yesterday, but today I cannot connect using the server's name (//tower).  I can connect using its IP address (192.168.0.115).  How can I get it to start responding to its name.  Restarting might do it, but is there another way?

 

I've telneted into the server (using the ip address) and used the top command.  It doesn't seem to be out of memory (9896k free).  Here are the last few lines of the log:

 

Jan 17 10:23:57 Tower emhttp[1012]: shcmd (230): /usr/sbin/hdparm -y /dev/hda >/dev/null
Jan 17 13:56:00 Tower emhttp[1012]: shcmd (231): /usr/sbin/hdparm -y /dev/hda >/dev/null
Jan 17 14:26:08 Tower dhcpcd[892]: broadcasting DHCP_REQUEST for 192.168.0.115
Jan 17 15:08:00 Tower emhttp[1012]: shcmd (232): /usr/sbin/hdparm -y /dev/hda >/dev/null
Jan 17 20:26:09 Tower dhcpcd[892]: broadcasting DHCP_DISCOVER
Jan 17 20:26:09 Tower ifplugd(eth0)[980]: Link beat lost.
Jan 17 20:26:10 Tower kernel: [4963836.130768] e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Jan 17 20:26:10 Tower kernel: [4963836.130774] e1000: eth0: e1000_watchdog_task: 10/100 speed: disabling TSO
Jan 17 20:26:11 Tower ifplugd(eth0)[980]: Link beat detected.
Jan 17 20:26:14 Tower dhcpcd[892]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.0.255
Jan 17 20:26:14 Tower dhcpcd[892]: dhcpIPaddrLeaseTime=172800 in DHCP server response.
Jan 17 20:26:14 Tower dhcpcd[892]: dhcpT1value is missing in DHCP server response. Assuming 86400 sec
Jan 17 20:26:14 Tower dhcpcd[892]: dhcpT2value is missing in DHCP server response. Assuming 151200 sec
Jan 17 20:26:14 Tower dhcpcd[892]: DHCP_OFFER received from  (192.168.0.1)
Jan 17 20:26:14 Tower dhcpcd[892]: broadcasting DHCP_REQUEST for 192.168.0.115
Jan 17 20:26:14 Tower dhcpcd[892]: dhcpIPaddrLeaseTime=172800 in DHCP server response.
Jan 17 20:26:14 Tower dhcpcd[892]: dhcpT1value is missing in DHCP server response. Assuming 86400 sec
Jan 17 20:26:14 Tower dhcpcd[892]: dhcpT2value is missing in DHCP server response. Assuming 151200 sec
Jan 17 20:26:14 Tower dhcpcd[892]: DHCP_ACK received from  (192.168.0.1)
Jan 18 09:25:32 Tower in.telnetd[16949]: connect from 192.168.0.20 (192.168.0.20)
Jan 18 09:25:46 Tower login[16950]: ROOT LOGIN  on `pts/0' from `192.168.0.20'

 

Thanks

 

Thinking the problem is with emhttp, I tried to find the parameters for that command and entered emhttp -?.  After a few seconds, it responded with nmbd: no process killed.  Somehow, I can now connect to //tower.  Any linux gurus care to explain what might have happened?

 

Here's what was in the logfile after doing that:

 

Jan 18 14:38:05 Tower emhttp[18056]: unRAID System Management Utility version 4.1
Jan 18 14:38:05 Tower emhttp[18056]: Copyright (C) 2005-2007, Lime Technology, LLC
Jan 18 14:38:05 Tower emhttp[18056]: Device inventory:
Jan 18 14:38:05 Tower emhttp[18056]: pci-0000:00:1f.1-ide-0:1 (hdb) ata-ST3300622A_XXXXXXXX
Jan 18 14:38:05 Tower emhttp[18056]: pci-0000:00:1f.1-ide-0:0 (hda) ata-Maxtor_6Y250P0_XXXXXXXX
Jan 18 14:38:05 Tower emhttp[18056]: pci-0000:00:1f.2-scsi-0:0:0:0 (sda) scsi-SATA_ST3320620AS_XXXXXXXX
Jan 18 14:38:05 Tower emhttp[18056]: pci-0000:01:04.0-ide-0:0 (hde) ata-Maxtor_6Y250P0_XXXXXXXX
Jan 18 14:38:05 Tower emhttp[18056]: shcmd (1): rmmod md-mod >>/var/log/go 2>&1
Jan 18 14:38:05 Tower emhttp[18056]: shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=8,0,3,0,3,64,33,0,0,0,0,0 >>/var/log/go 2>&1
Jan 18 14:38:21 Tower emhttp[18056]: shcmd (3): killall -w smbd nmbd
Jan 18 14:38:22 Tower emhttp[18056]: shcmd (4): /usr/sbin/nmbd -D
Jan 18 14:38:22 Tower emhttp[18056]: shcmd (5): /usr/sbin/smbd -D
Jan 18 14:38:22 Tower emhttp[18056]: can't bind listener socket: Address already in use

 

When the server name is not recognized, this usually means that one of the Samba daemon processes is not started (nmbd).  Next time this happens please post your system log.