nedbrew99

Members
 View Profile  See their activity

  • Posts

    10

  • Joined

  • Last visited

 Content Type 

Everything posted by nedbrew99

  1. nedbrew99
    Getting the error /usr/local/bin/code-server: line 1: syntax error near unexpected token `newline' /usr/local/bin/code-server: line 1: `<!DOCTYPE html>' /usr/local/bin/code-server: line 1: syntax error near unexpected token `newline' /usr/local/bin/code-server: line 1: `<!DOCTYPE html>' /usr/local/bin/code-server: line 1: syntax error near unexpected token `newline' /usr/local/bin/code-server: line 1: `<!DOCTYPE html>' /usr/local/bin/code-server: line 1: syntax error near unexpected token `newline' /usr/local/bin/code-server: line 1: `<!DOCTYPE html>' /usr/local/bin/code-server: line 1: syntax error near unexpected token `newline' /usr/local/bin/code-server: line 1: `<!DOCTYPE html>' GNOME_KEYRING_CONTROL=/root/.cache/keyring-GPKSC2 SSH_AUTH_SOCK=/root/.cache/keyring-GPKSC2/ssh No init file configured, skipping... GNOME_KEYRING_CONTROL=/root/.cache/keyring-VZ6TC2 SSH_AUTH_SOCK=/root/.cache/keyring-VZ6TC2/ssh No init file configured, skipping... GNOME_KEYRING_CONTROL=/root/.cache/keyring-IKAGC2 SSH_AUTH_SOCK=/root/.cache/keyring-IKAGC2/ssh No init file configured, skipping... GNOME_KEYRING_CONTROL=/root/.cache/keyring-YZ7GC2 SSH_AUTH_SOCK=/root/.cache/keyring-YZ7GC2/ssh No init file configured, skipping... GNOME_KEYRING_CONTROL=/root/.cache/keyring-CEU9C2 SSH_AUTH_SOCK=/root/.cache/keyring-CEU9C2/ssh No init file configured, skipping...
  2. nedbrew99
    is there any way to add the btmgmt tools? These are for bluetooth management.
  3. nedbrew99
    I have a few simple shares that are set to public and was able to access them without issue for a long time. Went away on vacation and when I came back I cannot access them anymore. I assume windows update broke something but am not sure where to start. AS a side note, a different machine on my home network can access them without issues. Not sure where to start troubleshooting. Had the windows SMB1 turned on, did the registry hack for InsucureGuest, still cannot access any shares. Cannot use \\HOMENAS or the \\ip_address to see anything. Just prompts for login information. Tried setting up a unraid user and password and using \\homenas\user for login and it does not work either. Any assistance appreciated.
  4. nedbrew99
    is there anything I can do to try and determine what specifically is the issue?
  5. nedbrew99
    I have been running 6.11.5 for over 6 months and in the last week it has started crashing out of the blue. I tried upgrading to 6.12.1 and that did not work so I rolled back to the previous (original) version. I have attached the syslog from the flash drive and the diagnostic zip. NOt sure where to look to figure out what has change/going wrong homenas-diagnostics-20230628-0400.zipsyslog
  6. nedbrew99
    after upgrading I am getting the following errors in the log 2023/06/25 12:23:39.073 HOMENAS Error system daemons Jun 25 12:23:39 HomeNas nmbd 2688 [2023/06/25 12:23:39.287077, 0] ../../source3/nmbd/nmbd.c:59(terminate) 2023/06/25 12:23:39.073 HOMENAS Error system daemons Jun 25 12:23:39 HomeNas nmbd 2688 Got SIGTERM: going down... 2023/06/25 12:23:39.073 HOMENAS Error system daemons Jun 25 12:23:39 HomeNas winbindd 2709 [2023/06/25 12:23:39.287097, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) 2023/06/25 12:23:39.073 HOMENAS Error system daemons Jun 25 12:23:39 HomeNas winbindd 2701 [2023/06/25 12:23:39.287107, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) 2023/06/25 12:23:39.073 HOMENAS Error system daemons Jun 25 12:23:39 HomeNas winbindd 2709 Got sig[15] terminate (is_parent=0) 2023/06/25 12:23:39.073 HOMENAS Error system daemons Jun 25 12:23:39 HomeNas winbindd 2701 Got sig[15] terminate (is_parent=1) 2023/06/25 12:23:39.073 HOMENAS Debug user-level Jun 25 12:23:39 HomeNas wsdd2 2698 'Terminated' signal received. 2023/06/25 12:23:39.073 HOMENAS Informational user-level Jun 25 12:23:39 HomeNas wsdd2 2698 terminating. 2023/06/25 12:23:41.237 HOMENAS Notice user-level Jun 25 12:23:41 HomeNas root Starting Samba: /usr/sbin/smbd -D 2023/06/25 12:23:41.260 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas smbd 5852 [2023/06/25 12:23:41.476295, 0] ../../source3/smbd/server.c:1741(main) 2023/06/25 12:23:41.260 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas smbd 5852 smbd version 4.17.7 started. 2023/06/25 12:23:41.260 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas smbd 5852 Copyright Andrew Tridgell and the Samba Team 1992-2022 2023/06/25 12:23:41.262 HOMENAS Notice user-level Jun 25 12:23:41 HomeNas root /usr/sbin/nmbd -D 2023/06/25 12:23:41.279 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas nmbd 5854 [2023/06/25 12:23:41.495684, 0] ../../source3/nmbd/nmbd.c:901(main) 2023/06/25 12:23:41.279 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas nmbd 5854 nmbd version 4.17.7 started. 2023/06/25 12:23:41.279 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas nmbd 5854 Copyright Andrew Tridgell and the Samba Team 1992-2022 2023/06/25 12:23:41.281 HOMENAS Notice user-level Jun 25 12:23:41 HomeNas root /usr/sbin/wsdd2 -d -4 2023/06/25 12:23:41.343 HOMENAS Informational user-level Jun 25 12:23:41 HomeNas wsdd2 5868 starting. 2023/06/25 12:23:41.343 HOMENAS Notice user-level Jun 25 12:23:41 HomeNas root /usr/sbin/winbindd -D 2023/06/25 12:23:41.364 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas winbindd 5869 [2023/06/25 12:23:41.580541, 0] ../../source3/winbindd/winbindd.c:1440(main) 2023/06/25 12:23:41.364 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas winbindd 5869 winbindd version 4.17.7 started. 2023/06/25 12:23:41.364 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas winbindd 5869 Copyright Andrew Tridgell and the Samba Team 1992-2022 2023/06/25 12:23:41.367 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas winbindd 5871 [2023/06/25 12:23:41.583627, 0] ../../source3/winbindd/winbindd_cache.c:3116(initialize_winbindd_cache) 2023/06/25 12:23:41.367 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas winbindd 5871 initialize_winbindd_cache: clearing cache and re-creating with version number 2 2023/06/25 12:23:41.383 HOMENAS Informational user-level Jun 25 12:23:41 HomeNas emhttpd shcmd (150): /etc/rc.d/rc.avahidaemon restart 2023/06/25 12:23:41.390 HOMENAS Notice user-level Jun 25 12:23:41 HomeNas root Stopping Avahi mDNS/DNS-SD Daemon: stopped 2023/06/25 12:23:41.391 HOMENAS Informational system daemons Jun 25 12:23:41 HomeNas avahi-daemon 2727 Got SIGTERM, quitting. 2023/06/25 12:23:41.391 HOMENAS Error system daemons Jun 25 12:23:41 HomeNas avahi-dnsconfd 2751 read(): EOF
  7. nedbrew99
    So I gave up on having the UNraid in Active Directory. I just has public shares in unraid and map folders accordingly. So far so good, but anyone can see anything. not a problem for my set-up but may be for others
  8. nedbrew99
    So I installed the pihole and it was working fine, now I cannot access the webui no matter what I try. I can ping it and if I open the console and do a pihole status it appears to be running. what can I do to get the webui back
  9. nedbrew99
    So I have an Active Directory set-up at my home and currently it is hit or miss if someone will be able to access the unraid shares. if I look in the logs I see certain users just randomly stop being able to access things. I just removed the idmap changes to the smb-extra, but it seems that the reboot is what actually fixes it for a day or two, then it randomly has someone not able to access the sahres
  10. nedbrew99
    Any updates on this as I am experiencing this exact issue. running 6.11.5 and have tried the change to set this in the smb-extras [global] idmap config * : backend = tdb idmap config * : range = 1000-7999 idmap config <shortname> : backend = rid idmap config <shortname>: range = 10000-4000000000 but was unable to access anything with windows file explorer and could not reset permissions no matter what I did. Had to set back to old set-up and is working for the moment