There is no “File Sharing” as shown on page 45, it doesn’t look like SAMBA is installed.
The ZFS tab shows:
# This package requires Samba
Install Samba software via your package manager
I’m not used to Rocky (RHEL), how do I fix cockpit so that it works?
Not a RHEL user but probably sudo yum install samba samba-client samba-common
I just did sudo dnf install samba to resolve that warning, though I don’t believe it causes any problems unless you want to use samba for filesharing.
You can run this using the terminal tab at the bottom of the sidebar.
yum command is superseded by dnf and now is just a symlink: /usr/bin/yum -> dnf-3
This did the trick
sudo dnf-3 install samba samba-client samba-common
Thanks
Hi All,
I can see that installing Samba fixed the issues. if you also want the file-sharing tab you can run
dnf install cockpit-file-sharing
This will install the package, you will need to refresh your browser to see the tab pop up.
This has been an extremely disappointing and frustrating experience, so I’ve got to the point that I am going replace Rocky Linux and Houston with TrueNAS.
I had to ssh onto the server to start cockpit, Samba and cockpit-packagekit.noarch weren’t installed.
Installing packagekit allowed me to update the system, which resulted in 421 packages being installed, although machine was less than a week old. So an ancient image is being used to install new machines.
The HL15 isn’t a desktop but the XServer is running, even Firefox and Thunderbird are installed, no idea why. It’s not as though someone is going to run this, with it’s 6 fans blowing away, as a desktop pc.
And now I can’t access the server via SMB, somehow it thinks it should bind to virbr0.
HI @Bill,
I’m sorry to hear about your experience with the HL15.
We aimed to deliver an all-around OS for multiple uses for customers of all types, whether that be someone who wants to use this as a NAS or a workstation.
The master image we utilized was created and updated just before we released the HL15. However, due to the overwhelming demand and continuous production, we haven’t had the opportunity to pause production and update the master image.
As for Firefox being installed, this is the default web browser that Rocky ships with and is not something we install after the fact. Most of the preinstalled packages on the server are from our default Rocky 8 desktop ISO.
The virbr0 is a virtual interface created when the tab of the virtual machine is installed in the cockpit. If you wish to remove this interface, you can simply remove the cockpit-machines and then adjust it in the networking section.
SMB, by default, does not bind to a specific interface and instead listens on all interfaces, so the virbr0 should not be causing any issues with SMB.
Could you provide more details about the SMB issue so that we can assist further? Your input is invaluable in helping us address any concerns you may have.
I’m guessing that SMB is not starting due to this:
And nmbd is binding to all the devices (incl. virbr0) but probably has nothing to announce due to the above.
And I don’t fancy debugging samba 
Hi @Bill, Can you share your /etc/samba/smb.conf folder and the output of “testparm -s”
it looks like there is an invalid line in the config file somewhere
Output of testparm -s:
Load smb config files from /etc/samba/smb.conf
Unknown parameter encountered: "includes"
Unknown parameter encountered: "includes"
Loaded services file OK.
Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback)
Server role: ROLE_STANDALONE
# Global parameters
[global]
printcap name = cups
registry shares = Yes
security = USER
workgroup = SAMBA
idmap config * : backend = tdb
cups options = raw
include = /etc/cockpit/zfs/shares/Main_Backups.conf
[Backups]
comment = ZFS: Main/Backups
include = /etc/cockpit/zfs/shares/Main_Multimedia.conf
path = /Main/Backups
read only = No
[Multimedia]
comment = ZFS: Main/Multimedia
path = /Main/Multimedia
read only = No
[homes]
browseable = No
comment = Home Directories
inherit acls = Yes
read only = No
valid users = %S %D%w%S
[printers]
browseable = No
comment = All Printers
create mask = 0600
path = /var/tmp
printable = Yes
[print$]
comment = Printer Drivers
create mask = 0664
directory mask = 0775
force group = @printadmin
path = /var/lib/samba/drivers
write list = @printadmin root
Output of cat /etc/samba/smb.conf:
# this config was generated by cockpit-file-sharing after importing smb.conf
# original smb.conf location:
# '/etc/samba/smb.conf' -> '/etc/samba/smb.conf.bak'
[global]
include = registry
# COCKPIT ZFS MANAGER
# WARNING: DO NOT EDIT, AUTO-GENERATED CONFIGURATION
include = /etc/cockpit/zfs/shares.conf
Output of cat /etc/samba/smb.conf.bak:
# See smb.conf.example for a more detailed config file or
# read the smb.conf manpage.
# Run 'testparm' to verify the config is correct after
# you modified it.
#
# Note:
# SMB1 is disabled by default. This means clients without support for SMB2 or
# SMB3 are no longer able to connect to smbd (by default).
[global]
workgroup = SAMBA
security = user
passdb backend = tdbsam
printing = cups
printcap name = cups
load printers = yes
cups options = raw
# Install samba-usershares package for support
include = /etc/samba/usershares.conf
# inclusion of net registry, inserted by cockpit-file-sharing:
include = registry
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @printadmin root
force group = @printadmin
create mask = 0664
directory mask = 0775
I think I see the issue with your share file.
Could you remove the “include = /etc/cockpit/zfs/shares/Main_Multimedia.conf” from under the Backups share and under global?
Also to make things simple could you also remove the “homes”“printers”“print$” shares and the below from the smb.conf
# COCKPIT ZFS MANAGER
# WARNING: DO NOT EDIT, AUTO-GENERATED CONFIGURATION
include = /etc/cockpit/zfs/shares.conf
Can you then make your shares using the cockpit-file-sharing tab and not in the ZFS tab. the shares in the ZFS manager tab are not used and we have since made the file-sharing tab instead
I have no idea where Samba is getting all from, it sure isn’t from smb.conf.
cat /ets/samba/smb.conf
# this config was generated by cockpit-file-sharing after importing smb.conf
# original smb.conf location:
# '/etc/samba/smb.conf' -> '/etc/samba/smb.conf.bak'
[global]
include = registry
testparm -s
Unknown parameter encountered: "includes"
Unknown parameter encountered: "includes"
Loaded services file OK.
Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback)
Server role: ROLE_STANDALONE
# Global parameters
[global]
printcap name = cups
registry shares = Yes
security = USER
workgroup = SAMBA
idmap config * : backend = tdb
cups options = raw
include = /etc/samba/usershares.conf
[homes]
browseable = No
comment = Home Directories
inherit acls = Yes
read only = No
valid users = %S %D%w%S
[printers]
browseable = No
comment = All Printers
create mask = 0600
path = /var/tmp
printable = Yes
[print$]
comment = Printer Drivers
create mask = 0664
directory mask = 0775
force group = @printadmin
path = /var/lib/samba/drivers
write list = @printadmin root
[Multimedia]
path = /Main/Multimedia
read only = No
[Backups]
path = /Main/Backups
read only = No
I removed the ZFS part, and as soon as I display the ZFS tab …
# COCKPIT ZFS MANAGER
# WARNING: DO NOT EDIT, AUTO-GENERATED CONFIGURATION
include = /etc/cockpit/zfs/shares.conf
is re-added!
Found it, samba can also use a Windows like registry. samba-regedit What an abomination!
HI @Bill, Can you confirm that SMB is now working for you after removing those lines?
No, I get an error on my windows machine and my linux machines when I attempt to connect to the shares.
Bill, can you share what that error is?
Does “testparm -s” still show the errors?
You will also need to open the firewall and make sure the SMB service is running.
I can see the shares:
But when I try to access one I get:
All the services are running:
Samba is enabled in the firewall:
testparm -s
Load smb config files from /etc/samba/smb.conf
Unknown parameter encountered: "includes"
Unknown parameter encountered: "includes"
Loaded services file OK.
Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback)
Server role: ROLE_STANDALONE
# Global parameters
[global]
printcap name = cups
registry shares = Yes
security = USER
workgroup = SAMBA
idmap config * : backend = tdb
cups options = raw
include = /etc/cockpit/zfs/shares.conf
[homes]
browseable = No
comment = Home Directories
inherit acls = Yes
read only = No
valid users = %S %D%w%S
[printers]
browseable = No
comment = All Printers
create mask = 0600
path = /var/tmp
printable = Yes
[print$]
comment = Printer Drivers
create mask = 0664
directory mask = 0775
force group = @printadmin
path = /var/lib/samba/drivers
write list = @printadmin root
[Multimedia]
path = /Main/Multimedia
read only = No
valid users = 45drives
[Backups]
path = /Main/Backups
read only = No
valid users = %D%w%S %S 45drives
cat /etc/samba/smb.conf
# this config was generated by cockpit-file-sharing after importing smb.conf
# original smb.conf location:
# '/etc/samba/smb.conf' -> '/etc/samba/smb.conf.bak'
[global]
include = registry
# COCKPIT ZFS MANAGER
# WARNING: DO NOT EDIT, AUTO-GENERATED CONFIGURATION
include = /etc/cockpit/zfs/shares.conf
The ZFS Manager injected itself when I opened to the ZFS tab.
Bill,
can you go to the ZFS tab and on the top right click the drop down by the refresh and go to the “configure cockpit zfs manager”
In that screen could you make the options match this:
once this is done can you then remove the include ZFS lines from the SMB.conf
# COCKPIT ZFS MANAGER
# WARNING: DO NOT EDIT, AUTO-GENERATED CONFIGURATION
include = /etc/cockpit/zfs/shares.conf
Also in the filesharing tab can you make sure there is nothing specified in the global section? Our filesharing tab uses netconf to configure the shares so running “netconf list” will show all the options and will show what the filesharing tab is adding to the SMB configuration.
If you wish to use the CLI you can also export the net conf into a file then edit the file and import it back again with the following
# export to a file
net conf list > file
# edit the file
vim file
# importing the file
net conf import file