justgosh

Members
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About justgosh

  • Rank
    Newbie
  1. justgosh

    500 Internal Server Error

    Bump
  2. justgosh

    500 Internal Server Error

    Any suggestions on following would be appreciated. I still haven't figured out why it lost bits of the configuration. The files are all still present. Even though I've made the changes, it's not logging errors. Ultimately, I can't figured out hot to fix the 500 error.
  3. justgosh

    500 Internal Server Error

    I'm running DSM 4.3 build 3810++ (repack v1.0), but I get the feeling this might help out others So, I've been running the build, testing, for several months on 2 systems. One seems to occasionally have several services crash while the other has been rock solid until several days ago. Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, admin and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. Also, it's forgotten it's static IP iSCSI services still launch (and work) Samba was working Logged in as root /usr/syno/etc/rc.d/S97apache-sys.sh restart No affect Tried rebooting For a laugh, I reissued certs cd /usr/syno/etc/ssl/ ./mkcert.sh Edited /etc/synoinfo.conf and set runHTTPS="no" /usr/syno/etc/rc.d/S97apache-sys.sh restart Now I'm look it at the same issue but without SSL Edited /usr/syno/apache/conf/httpd.conf-sys ErrorLog /var/log/httpd-error-sys.log #ErrorLog /dev/null Edited /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes to DEVICE=eth0 BOOTPROTO=static ONBOOT=yes IPADDR=192.168.. NETMASK=255.255.255.0 Edited /etc/sysconfig/network-scripts/ifcfg-eth1 DEVICE=eth1 BOOTPROTO=dhcp ONBOOT=yes to DEVICE=eth1 BOOTPROTO=static ONBOOT=yes IPADDR=192.168.. NETMASK=255.255.255.0 /etc/rc.network restart So my device is back up, but management is still down. I've looked in the /var/log/httpd-error-sys.log file, but it's empty. Any advice?
  4. justgosh

    System is getting ready. Please login later.

    Issue just popped up on 4.3. Some of the services were running fine. Rebooting did not resolve. synobootseq --set-boot-done synobootseq --is-ready /usr/syno/etc/rc.d/S97apache-sys.sh start and everything was happy again, Thanks! EDIT - Actually, I spoke too soon. I'm getting The operation failed. Please log in to DSM again and retry. Errors throughout the configuration.
  5. justgosh

    N54L 100MByte/sec Transfer speed

    @HDMann, I see where you are going and I'm not offended. I have raptors and 840s in the other NAS. The File Server has the bandwidth to saturate a gig port. The SQL has the bandwidth to saturate. The switch has more than enough to support what I'm testing 24 times over. Added the 5th drive. Rebuilt the array. Only saw a marginal improvement. Ran Bios update 2011.07.29, ran 2013.10.01, pulled the 5th drive, rebuilt the array and bam 98MB. I think issues may have been caused by going from 2011.07.29 to a Russian mod to bay. I think there may have been flags checked in the bios that I was no longer able to see or that there was a disconnect with the speed selection or write. Either way, it's acting like it should now. Honestly, a few months ago I setup a N54L Solaris array that was giving me really low bandwidth, so I shelved the whole thing. I've never used Reds before so I thought they were the likely issue. About a week ago I read someone talking about xpenology as the fastest NAS OS they'd tried... Also saw someone mention they were using Reds and getting 110MB. Pulled the aborted project down, install xpenology but ran into the same low bandwidth issue again. My post and then Zarocq's response. Seriously Zarocq, knowing that it could work made all the difference. Thanks again.
  6. justgosh

    N54L 100MByte/sec Transfer speed

    @HDMann, I see where you are going and I'm not offended. I have raptors and 840s in the other NAS. The File Server has the bandwidth to saturate a gig port. The SQL has the bandwidth to saturate. The switch has more than enough to support what I'm testing 24 times over. Added the 5th drive. Rebuilt the array. Only saw a marginal improvement. Ran Bios update 2011.07.29, ran 2013.10.01, pulled the 5th drive, rebuilt the array and bam 98MB. I think issues may have been caused by going from 2011.07.29 to a Russian mod to bay. I think there may have been flags checked in the bios that I was no longer able to see or that there was a disconnect with the speed selection or write. Either way, it's acting like it should now. Honestly, a few months ago I setup a N54L Solaris array that was giving me really low bandwidth, so I shelved the whole thing. I've never used Reds before so I thought they were the likely issue. About a week ago I read someone talking about xpenology as the fastest NAS OS they'd tried... Also saw someone mention they were using Reds and getting 110MB. Pulled the aborted project down, install xpenology but ran into the same low bandwidth issue again. My post and then Zarocq's response. Seriously Zarocq, knowing that it could work made all the difference. Thanks again.
  7. justgosh

    N54L 100MByte/sec Transfer speed

    Running Native. Zarocq, Thank you. That's incredibly helpful. Is that 100 on reads and 100 on writes? I will look over everything again in my test environment but any pointers, advice, or settings recommendations would be appreciated. I don't thing the number of drives is the issue, but will also send off for 2 more drives.
  8. justgosh

    N54L 100MByte/sec Transfer speed

    Native and LAN Speed Test by totusoft.com from several locations. I've tested vm's, physical servers, desktops, laptops, x-over direct, and even tried multiple simultaneous connections to measure the aggregate. It peaks at 60, but averages around 55 write and 30 read. I'm willing to use any other utility though. Here are my thoughts. 1. I've setup something wrong. 2. That's just the speed of the thing. In order to eliminate #2, I thought I would ask about setups and throughput. If everyone running WD reds is seeing 60MB and the folks running seagate are running 110, it might be time to swap. If they are all running a cache drive, it's time to buy an SSD. No one seems to be posting builds and speeds Thoughts?
  9. justgosh

    N54L 100MByte/sec Transfer speed

    Great point sinnuendo. These drives have very low IOPS so I'm using 4gb files. What are your BIOS settings? Mine is setup the same as this tut http://homeservershow.com/hp-proliant-n ... sited.html I'd love to run iperf to eliminate some of the network thoughts, but I'm not totally sure where to get it for XPEnology... it's not the marvel version is it?
  10. justgosh

    N54L 100MByte/sec Transfer speed

    I've seen a few posts stating that people were able to achieve 100MByte/sec read/write speed using xpenology on their N54L. I was wondering what your setup looks like and what tools you were using to measure. Mine is currently: N54L 16GB ram 4x 3tb WD Red 1 volume SHR No SSD Cache Bay Bios XPEnology DS3612xs DSM 4.3 build 3810++ (repack v1.0) Catalyst 2970 60MB/sec windows transfer Apologies in advance if this has already been posted I've spent a few days looking, but the search says N54L is a common term so it's pretty hard to find info related