Napp-IT smb

ekke · Nov 1, 2017

My smb/cifs service is down and I cant enable it . Any idees?

Edit: SOlved

gea · Nov 2, 2017

Can you try a reboot?

ekke · Nov 2, 2017

I accidently typed "reboot now" and now Im stuck . "beadm activate omnios-5" etc. doesn't help

Dropbox - omnibeadm.PNG

ekke · Nov 2, 2017

If I manually choose a be in the boot options I can get into the OS again, another little annoyance

I think I found a error that could be the cause of all this

"
usage: smbutil view [connection options] //[workgroup;][user[

assword]@]server
root@omnios:~# sharemgr start -P smb zfs
SMB: Unable to enable service
SMB: Unable to enable service
SMB: Unable to enable service
SMB: Unable to enable service
root@omnios:~# svcadm enable -r smb/server
svcadm: svc:/milestone/network depends on svc:/network/physical, which has multiple instances.
root@omnios:~#
"

"
root@omnios:~# svcs -l smb/server
fmri svc:/network/smb/server:default
name smbd daemon
enabled true
state offline
next_state none
state_time Thu Nov 2 22:09:59 2017
restarter svc:/system/svc/restarter:default
dependency require_any/error svc:/milestone/network (online)
dependency require_all/error svc:/system/filesystem/local (maintenance)
dependency require_all/none svc:/system/idmap:default (online)
dependency require_all/none svc:/network/smb/client:default (offline)
"

ekke · Nov 2, 2017

Added more info in pastebin ; " usage: smbutil view [connection options] //[workgroup;][user[:password]@]serv - Pastebin.com

Dropbox - omniboot.PNG

gea · Nov 3, 2017

ekke said:
dependency require_all/error svc:/system/filesystem/local (maintenance)

SMB sharing onSolarish is an integrated part of a filesystem, a ZFS property.
It seems that you have a problem with a filesystem

check /var/svc/log/system-filesystem-local:default.log

then try to delete the maintenance state

Code:

#svcadm -v clear svc:/system/filesystem/local:default
#svcadm -v enable svc:/system/filesystem/local:default

and retry to start SMB

Can you check system logs
- napp-it menu System > Logs and System > Faults

- check if all filesystems are mounted (console ot napp-it cmd field)
zfs get all | grep mounted

About your bootproblem
'reboot now' tries to to boot into a BE now (result: BE now not found)

Reboot on Solaris is simply 'reboot' or 'init 6'

ekke · Nov 3, 2017

Didn't help unfortunately, thanx for the help btw.
Can I export my settings via CLI and reinstall ?

SMBfail - Pastebin.com

This was interesting

root@omnios:~# pkg verify
PACKAGE STATUS
pkg://omnios/SUNWcs ERROR
file: lib/svc/manifest/system/keymap.xml
ERROR: Size: 4832 bytes should be 4835
ERROR: Hash: c4ab64884fe769201c498813cd44660b2e9773c3 should be bac5dc062bb31b946dc03342f88cca4bdea89351
file: usr/bin/which
ERROR: Mode: 0700 should be 0555
pkg://omnios/SUNWcsd ERROR
dir: dev/zcons
ERROR: Group: 'root (0)' should be 'sys (3)'
pkg://omnios/security/sudo ERROR
file: etc/sudoers
ERROR: Mode: 0640 should be 0440
pkg://omnios/system/boot/real-mode ERROR
file: boot/solaris/bootenv.rc
ERROR: Group: 'root (0)' should be 'sys (3)'
pkg://omnios/web/ca-bundle ERROR
dir: etc/ssl/certs
ERROR: Mode: 0700 should be 0755

The only change I did was a pkg update and reboot on 29/9
SMB fails even if I use a BE from before 29/9 though.

gea · Nov 4, 2017

The situation is quite unclear.
I would indeed export the pool and do a reinstall of OmniOS now as this is much faster than error seeking.

You can backup the napp-it configuration to a datapool with Jobs > Backup and optionally restore in menu users (Pro Feature). On CLI you can simply save the folder /var/web-gui/_log and ../_my, then reinstall OS+napp-it and restore these two folders + pool import.

btw
Propably on monday, the next OmniOS CE stable 151024 is expected

ekke · Nov 4, 2017

what about lx zones? just export the configs and after import of the pool import the config somehow?

gea · Nov 4, 2017

The LX data/VMs is on your datapool. OmniOS saves cfgs in /etc/zones. If you have created LX zones in napp-it you should be ok without restoring /etc/zones

What I would do is using a new bootdisk, setup, import pool and check if you can add your former zones. On problems you have your old bootdisk available

btw
I saw your error message at OmniOS Lobby

Code:

cannot mount '/data/zones': directory is not empty

This can occur if a filesystem is not mounted by error and a process writes to it later. It writes then data to a regular folder. A later ZFS mount command expects an empty folder and fails.

Check content of /data/zones
It must be empty if the ZFS filesystem is not mounted. If there is data inside delete or move elsewhere and mount data/zones. Optionally place data there then.

ekke · Nov 6, 2017

I remembered that I did a zoneadm /z xxxx move /data/zones/xxxx before

Dropbox - zones.PNG

moved em back now but i still cant start cif service

root@omnios:/tank# svcadm enable -r smb/server
svcadm: svc:/milestone/network depends on svc:/network/physical, which has multiple instances.

root@omnios:/tank# svcs -xv
svc:/system/filesystem/local:default (local file system mounts)
State: maintenance since Fri Nov 3 23:10:39 2017
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: SMF-8000-KS
See: /var/svc/log/system-filesystem-local:default.log
Impact: 23 dependent services are not running:
svc:/milestone/multi-user:default
svc:/application/management/net-snmp:default
svc:/system/intrd:default
svc:/milestone/multi-user-server:default
svc:/system/zones:default
svc:/system/system-log:default
svc:/network/smtp:sendmail
svc:/network/sendmail-client:default
svc:/system/filesystem/autofs:default
svc:/system/dumpadm:default
svc:/system/fmd:default
svc:/network/inetd:default
svc:/system/cron:default
svc:/network/nfs/status:default
svc:/network/nfs/nlockmgr:default
svc:/network/nfs/server:default
svc:/system/hotplug:default
svc:/network/smb/server:default
svc:/network/shares/group:default
svc:/network/shares/group:smb
svc:/network/shares/group:zfs
svc:/system/boot-archive-update:default
svc:/system/sac:default

svc:/network/rpc/gss:default (Generic Security Service)
State: uninitialized since Thu Nov 2 23:37:12 2017
Reason: Restarter svc:/network/inetd:default is not running.
See: SMF-8000-5H
See: man -M /usr/share/man -s 1M gssd
Impact: 11 dependent services are not running:
svc:/network/smb/client:default
svc:/milestone/multi-user:default
svc:/application/management/net-snmp:default
svc:/system/intrd:default
svc:/milestone/multi-user-server:default
svc:/system/zones:default
svc:/network/smb/server:default
svc:/network/shares/group:default
svc:/network/nfs/server:default
svc:/network/shares/group:smb
svc:/network/shares/group:zfs

svc:/network/rpc/smserver:default (removable media management)
State: uninitialized since Thu Nov 2 23:37:12 2017
Reason: Restarter svc:/network/inetd:default is not running.
See: SMF-8000-5H
See: man -M /usr/share/man -s 1M rpc.smserverd
Impact: 2 dependent services are not running:
svc:/milestone/multi-user-server:default
svc:/system/zones:default

"svcadm: svc:/milestone/network depends on svc:/network/physical, which has multiple instances." does my physcical adapter have multiple instances?!

not that I can see
root@omnios:/tank/zonecfgfiles# ipadm show-if
IFNAME STATE CURRENT PERSISTENT
lo0 ok -m-v------46 ---
igb0 failed bm--------46 -46
igb1 ok bm--------46 -46
cxgbe0 ok bm--------46 -46
cxgbe1 failed bm--------46 -46

root@omnios:/tank/zonecfgfiles# dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
igb0 Ethernet down 0 half igb0
igb1 Ethernet up 1000 full igb1
cxgbe0 Ethernet up 10000 full cxgbe0
cxgbe1 Ethernet down 0 unknown cxgbe1

ekke · Nov 6, 2017

ekke said:
I accidently typed "reboot now" and now Im stuck . "beadm activate omnios-5" etc. doesn't help

Dropbox - omnibeadm.PNG

I found out why Omnios always tries to boot into now
Dropbox - bootfile.PNG

bootfile=now

now the question is what is the default, or any valid property for bootfile?

gea · Nov 6, 2017

The default one is the BE that is activated (see menu Snaps > Bootenvironments) and this is the most current as any file modifications go into this one when booted into.

If you want to select another BE during boot you may use the newest (they are sorted by date). If you want to remain within another BE, you must activate as on reboot you boot automatically the default.

btw
Zones are independent from services in the global zone.
Your problem seems a ZFS filesystem, a nonempty folder where a filesystem should be mounted or a OS problem.

ekke · Nov 7, 2017

gea said:
The default one is the BE that is activated (see menu Snaps > Bootenvironments) and this is the most current as any file modifications go into this one when booted into.

If you want to select another BE during boot you may use the newest (they are sorted by date). If you want to remain within another BE, you must activate as on reboot you boot automatically the default.

btw
Zones are independent from services in the global zone.
Your problem seems a ZFS filesystem, a nonempty folder where a filesystem should be mounted or a OS problem.

No matter what I choose as BE with beadm activate or in the boot meny from entering"6" bootfile=new .
I will try and manually edit the bootfile property when I get back from work.

the ZFS issue with the pool data and /data/zones is solved. I have removed all files from that path.

Edit: all smb et.al. services are running now.

Search

Napp-IT smb

ekke

Member

gea

Well-Known Member

ekke

Member

ekke

Member

ekke

Member

gea

Well-Known Member

ekke

Member

gea

Well-Known Member

ekke

Member

gea

Well-Known Member

ekke

Member

ekke

Member

gea

Well-Known Member

ekke

Member