ML
    • Register
    • Login
    • Search
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups

    Samba Issues

    IT Discussion
    linux samba fedora
    5
    16
    768
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Obsolesce
      Obsolesce last edited by scottalanmiller

      There's Fedora Samba file server that's very infrequently accessed. I only noticed this today because I needed to access it, so I'm not sure when it started.

      This was set up about 1.5 months ago, and was working great, rebooted since then, working fine.

      Now today, I try to access the server... no luck.

      0_1526411305557_968cf9eb-b213-443d-b181-e048719d4ddc-image.png

      1 Reply Last reply Reply Quote 2
      • momurda
        momurda last edited by

        @obsolesce said in Samba Issues:

        There's Fedora Samba file server that's very infreque

        Try
        journalctl -u smb.service -b
        to see a log of this service since boot

        Obsolesce 1 Reply Last reply Reply Quote 1
        • Obsolesce
          Obsolesce @momurda last edited by

          @momurda said in Samba Issues:

          @obsolesce said in Samba Issues:

          There's Fedora Samba file server that's very infreque
          

          Try
          journalctl -u smb.service -b
          to see a log of this service since boot

          I've since rebooted and gives the same output as pictured.

          1 Reply Last reply Reply Quote 1
          • momurda
            momurda last edited by

            First thing is to always check /var/log/whateverisntworking
            /var/log/samba should have your logs there.

            Obsolesce 1 Reply Last reply Reply Quote 1
            • Obsolesce
              Obsolesce @momurda last edited by

              @momurda said in Samba Issues:

              First thing is to always check /var/log/whateverisntworking
              /var/log/samba should have your logs there.

              Those say the same thing.

              1 Reply Last reply Reply Quote 1
              • momurda
                momurda last edited by

                Cant be the only log information in your logs, unless you dont have logging turned on.
                If it is you need to change smb.conf to allow more verbose logging.

                Obsolesce 1 Reply Last reply Reply Quote 0
                • Obsolesce
                  Obsolesce @momurda last edited by

                  @momurda said in Samba Issues:

                  Cant be the only log information in your logs, unless you dont have logging turned on.
                  If it is you need to change smb.conf to allow more verbose logging.

                  The errors are pictured at the top and seem clear, I just don't know how to fix it, or what they mean exactly... a bunch of google searching shows a lot of fixes that don't work or apply.

                  1 Reply Last reply Reply Quote 1
                  • black3dynamite
                    black3dynamite last edited by

                    I know I say this a lot, but could it be an SELinux permission?

                    1 Reply Last reply Reply Quote 0
                    • dafyre
                      dafyre last edited by

                      I would also suggest taking a close look at the logs. It's screaming about not having enough Memory... How much RAM do you have on the server -- and do you have a swapfile enabled?

                      1 Reply Last reply Reply Quote 2
                      • momurda
                        momurda last edited by

                        you can try
                        testparm /etc/samba/smb.conf
                        to see if there is an error in the config
                        If not, something else is wrong.

                        Obsolesce 1 Reply Last reply Reply Quote 2
                        • Obsolesce
                          Obsolesce @momurda last edited by

                          @momurda said in Samba Issues:

                          you can try
                          testparm /etc/samba/smb.conf
                          to see if there is an error in the config
                          If not, something else is wrong.

                          All's well there.

                          Load smb config files from /etc/samba/smb.conf
                          rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
                          Processing section "[share1]"
                          Processing section "[share2]"
                          Processing section "[share3]"
                          Loaded services file OK.
                          WARNING: You have some share names that are longer than 12 characters.
                          These may not be accessible to some older clients.
                          (Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
                          Server role: ROLE_DOMAIN_MEMBER
                          
                          Press enter to see a dump of your service definitions
                          
                          
                          1 Reply Last reply Reply Quote 1
                          • Obsolesce
                            Obsolesce last edited by Obsolesce

                            I got it working with Winbind, after reinstalling the OS (Fedora 28). The same issue persisted using sssd even after a new install. So Winbind it is, something changed somewhere via an update or something, because it was working a month ago, and there were no configuration changes from me.

                            I had /home as a separate LVM partition, so reinstalling from netinstall (minimal) was easy without losing /home, which has about 9TB of data in it.

                            I'll post a fix once I unscramble my notes.

                            1 Reply Last reply Reply Quote 3
                            • Obsolesce
                              Obsolesce last edited by

                              I posted the fix here: https://www.timothygruber.com/linux/samba-file-server-with-microsoft-ad/#Install_Packages

                              Basically, you add the --client-software=winbind switch to your realm join command, making sure you have the pre-reqs and correct SAMBA configuration afterwards.

                              momurda 1 Reply Last reply Reply Quote 2
                              • momurda
                                momurda @Obsolesce last edited by

                                @obsolesce Did you change your username?

                                Obsolesce scottalanmiller 2 Replies Last reply Reply Quote 0
                                • Obsolesce
                                  Obsolesce @momurda last edited by

                                  @momurda said in Samba Issues:

                                  @obsolesce Did you change your username?

                                  Yes, due to some personal reasons.
                                  </nameChangeTopic>

                                  1 Reply Last reply Reply Quote 1
                                  • scottalanmiller
                                    scottalanmiller @momurda last edited by

                                    @momurda said in Samba Issues:

                                    @obsolesce Did you change your username?

                                    The old one was... obsolete.

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post