I had a working Solaris 2009.06 server, home NAS, that's been working at
various software levels for some time. This morning it showed 28 days uptime,
and I hadn't been logged in for most of that time, i.e. I "really" didn't
change anything there :-(.
Also this morning, I couldn't access the filesystems from my Windows box, which
I normally spend hours every day doing. I could ping it, and I could SSH to
it, but I could not get the CIFS connections to succeed. I tried to establish
new mappings, no dice.
A typical attempt to connect looks like this:
C:\Documents and Settings\play>net use z: \\fsfs\ddb\Documents * /user:ddb
Type the password for \\fsfs\ddb\Documents:
System error 67 has occurred.
The network name cannot be found.
Same thing happens when I use the IP address instead of the host name.
Rebooted Solaris and Windows, no change. Turned off Windows firewall, no
change. Tried coming in from a laptop that's configured to access the file
server, no change. Hence I'm pretty sure that the problem is on the Solaris
end -- that laptop has been powered off since I last had it connected to the
file server, it hasn't had even automatic sofware updates in that time.
I'm very weak on Solaris sysadmin stuff, but I think it's telling me that IT
thinks everything is fine:
bash-3.2# svcs -l smb/server
fmri svc:/network/smb/server:default
name smbd daemon
enabled true
state online
next_state offline
state_time Sat Nov 07 15:15:36 2009
logfile /var/svc/log/network-smb-server:default.log
restarter svc:/system/svc/restarter:default
contract_id 68
dependency require_any/error svc:/milestone/network (online)
dependency require_all/error svc:/system/filesystem/local (online)
dependency require_all/error svc:/system/idmap:default (online)
The command "sharemgr list" hangs; that's probably a symptom that means
something. Anybody know what? (It can be terminated by CTRL-C).
The root and data zpools are both fine (state ONLINE, all vdevs ONLINE, no
errors).
The only thing I'm aware of changing was on the windows box, updating AVG free
8.5 to 9.0. Uninstalling that makes no difference. The laptop was still
running 8.5, and it fails in the same way. Hence the evidence suggests to me
that that's not the root cause. But I mention it, since it's the only thing I
know changed anywhere.
The service log has suspicious stuff that doesn't tell me what to do in it.
Things seem find since what I think is the last reboot, 9-Oct. I started
playing around 1:15 this afternoon, so the entries there are after the problem.
So there's no log entry in the file when the problem started.
However, the timeouts clearly indicate some sort of problem now. Problem is I
have no clue WHAT. Anybody have suggestions?
[ Oct 9 20:38:35 Executing start method ("/usr/lib/smbsrv/smbd start"). ]
smbd: NetBIOS services started
[ Oct 9 20:38:37 Method "start" exited with status 0. ]
[ Nov 7 13:19:08 Enabled. ]
[ Nov 7 13:19:28 Executing start method ("/usr/lib/smbsrv/smbd start"). ]
smbd: NetBIOS services started
[ Nov 7 13:19:31 Method "start" exited with status 0. ]
[ Nov 7 15:15:36 Stopping because service restarting. ]
[ Nov 7 15:15:36 Executing stop method (:kill). ]
[ Nov 7 15:16:37 Method or service exit timed out. Killing contract 68. ]
[ Nov 7 15:16:38 Method or service exit timed out. Killing contract 68. ]
[ Nov 7 15:16:39 Method or service exit timed out. Killing contract 68. ]
[ Nov 7 15:16:40 Method or service exit timed out. Killing contract 68. ]
--
This message posted from opensolaris.org
_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
