Kill3r

Members
 View Profile  See their activity

  • Posts

    12

  • Joined

  • Last visited

 Content Type 

Posts posted by Kill3r

    Web Server isnt starting

    in General Support

    Posted

    ok, answered my own question

     

    after checking the /var/log/syslog found this entry below, i was messing with my own ssl cert about a week ago, and this was the first reboot since.

     

    nginx: [emerg] cannot load certificate key "/boot/config/ssl/certs/UnRaid_unraid_bundle.pem": PEM_read_bio_PrivateKey() failed (SSL: error:2807106B:UI routines:UI_process:processing error:while reading strings error:0906406D:PEM routines:PEM_def_callback:problems getting password error:0907B068:PEM routines:PEM_read_bio_PrivateKey:bad password read)

     

    so i renamed the UnRaid_unraid_bundle.pem and rebooted, its now back

     

    Web Server isnt starting

    in General Support

    Posted · Edited by Kill3r

    Hi All

     

    Im having an issue after upgrading the 6.11 rc5 (from 6.11 rc4) after the update i cant access the web gui.  Although emhttp appears to start,, below is the Listening ports via netstat, there is no 80 or 443, but there is reference to emhttpd.socket listening.  I have downgraded back to 6.11 rc4, but the issue still exists.  Any Advise??

     

    netstat -anp | grep LISTEN
    tcp        0      0 0.0.0.0:2049            0.0.0.0:*               LISTEN      -
    tcp        0      0 0.0.0.0:3702            0.0.0.0:*               LISTEN      6479/wsdd2
    tcp        0      0 0.0.0.0:3702            0.0.0.0:*               LISTEN      6479/wsdd2
    tcp        0      0 0.0.0.0:3493            0.0.0.0:*               LISTEN      4214/upsd
    tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      6464/smbd
    tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      6508/rpcbind
    tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      6273/sshd: /usr/sbi
    tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      6464/smbd
    tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      6479/wsdd2
    tcp        0      0 0.0.0.0:5355            0.0.0.0:*               LISTEN      6479/wsdd2
    tcp        0      0 0.0.0.0:57107           0.0.0.0:*               LISTEN      6532/rpc.mountd
    tcp        0      0 0.0.0.0:40857           0.0.0.0:*               LISTEN      -
    tcp        0      0 0.0.0.0:43415           0.0.0.0:*               LISTEN      6532/rpc.mountd
    tcp        0      0 0.0.0.0:48833           0.0.0.0:*               LISTEN      6532/rpc.mountd
    tcp        0      0 0.0.0.0:48531           0.0.0.0:*               LISTEN      6512/rpc.statd
    tcp6       0      0 :::2049                 :::*                    LISTEN      -
    tcp6       0      0 :::445                  :::*                    LISTEN      6464/smbd
    tcp6       0      0 :::111                  :::*                    LISTEN      6508/rpcbind
    tcp6       0      0 :::22                   :::*                    LISTEN      6273/sshd: /usr/sbi
    tcp6       0      0 :::139                  :::*                    LISTEN      6464/smbd
    tcp6       0      0 :::53587                :::*                    LISTEN      6512/rpc.statd
    tcp6       0      0 :::35781                :::*                    LISTEN      6532/rpc.mountd
    tcp6       0      0 :::39643                :::*                    LISTEN      6532/rpc.mountd
    tcp6       0      0 :::38389                :::*                    LISTEN      6532/rpc.mountd
    tcp6       0      0 :::46505                :::*                    LISTEN      -
    unix  2      [ ACC ]     STREAM     LISTENING     49473    4210/blazer_usb      /var/run/nut/blazer_usb-ups
    unix  2      [ ACC ]     SEQPACKET  LISTENING     10701    1070/udevd           /run/udev/control
    unix  2      [ ACC ]     STREAM     LISTENING     13639    6280/inetd           /var/run/emhttpd.socket
    unix  2      [ ACC ]     STREAM     LISTENING     22937    6469/nmbd            /var/run/samba/nmbd/unexpected
    unix  2      [ ACC ]     STREAM     LISTENING     38777    6482/winbindd        /var/run/samba/winbindd/pipe
    unix  2      [ ACC ]     STREAM     LISTENING     49772    6508/rpcbind         /var/run/rpcbind.sock
    unix  2      [ ACC ]     STREAM     LISTENING     53447    6544/avahi-daemon:   /run/avahi-daemon/socket
    unix  2      [ ACC ]     STREAM     LISTENING     50633    6572/php-fpm: maste  /var/run/php5-fpm.sock
    unix  2      [ ACC ]     STREAM     LISTENING     38778    6482/winbindd        /var/lib/samba/winbindd_privileged/pipe
    unix  2      [ ACC ]     STREAM     LISTENING     65074    6718/unraid-api      /var/run/unraid-api.sock
    unix  2      [ ACC ]     STREAM     LISTENING     42020    1590/mcelog          /var/run/mcelog-client
    unix  2      [ ACC ]     STREAM     LISTENING     36527    1760/dbus-daemon     /var/run/dbus/system_bus_socket
    unix  2      [ ACC ]     STREAM     LISTENING     19864    1809/acpid           /var/run/acpid.socket
     

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted · Edited by Kill3r
    edit

    12 minutes ago, Kill3r said:

    Any thing i can do from a Unraid perspective to attempt to change the SCSI ID? 

    Hi have just found a similar issue on ESXi which is a HP driver based issue (fixed in hpsa-2.0.18), how can i find out what driver version Unraid is using for the HP controller? and can i replace the driver as a test? 

     

    I do realise this is technically falling outside of the UD plugin now too.

     

    Thanks

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted · Edited by Kill3r
    Clarity

    Hi All 

     

    Having a strange with 2 New SSD's where they are reporting the same SCSI ID/WWN, this is causing an issue where only one can be online at a time, else UnRaid fills the logs with one of the following, dependant on which drive is online. 

     

    May 27 11:53:16 UnRaid emhttpd: device /dev/sdx problem getting id

    May 27 12:19:29 UnRaid emhttpd: device /dev/sdy problem getting id

     

    Both drives function when only one is plugged in, but i was going to make a cache pool out of the pair, which i obviously cant do unless i can get them both online.

     

    As you can see from the attached images, both disks have _32020202020202020 appended to the model/serial, is this a drive issue, or something i can change from within UnRaid?

     

    Images are to show the various stats of both drives being online individually, also does not matter if i remove the drives from the historic Devices

    UD1.jpg

    One Drive Plugged in

    UD2.jpg

    Adding a second pushes the first into historic devices

    UD3.jpg

    removed from historic

    UD4.jpg

    reinserted the first which pushes the second to Historic Devices

     

    Thanks

    My Servers Early Access Plugin

    in Announcements

    Posted · Edited by Kill3r

    Hi

     

    Any plans to allow the download of the SSL cert and Key, I already have 443 forwarded to a Nginx Proxy, so i would like to set up a new proxy host for this work, is that possable? 

     

    Or can we use our own ssl certs (assume this isnt possable) due to the reliance on the unraid.net domain.

     

    Thanks

    unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables

    in User Customizations

    Posted · Edited by Kill3r
    more info

    Hi

     

    im a new Unraid user, still in trial mode, running 6.9.1, on a HP DL380 G8, with the inbuilt P420i in HBA mode, with 20 x 600GB 10K sas drives (got them stupidly cheap) :)

     

    i tried to run this script this morning and got a few issues appear during the run cycle.

     

    ./unraid6x-tunables-tester.sh: line 1546: [: : integer expression expected
    ./unraid6x-tunables-tester.sh: line 1548: [: : integer expression expected
    ./unraid6x-tunables-tester.sh: line 1550: [: : integer expression expected

     

    and

    Setting all drives to nr_requests=128 for the following tests/usr/local/sbin/mdcmd: line 11: echo: write error: Invalid argument

    /usr/local/sbin/mdcmd: line 11: echo: write error: Invalid argument

     

    are these expected? or is this a unraid/script versioning related issue?

     

    Thanks