NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
User.log and Spooler_Error.log Report Problems
I have a ReadyNAS PRO Business with 6 500G drives. It has worked for years without any real problems.
Looking throught the logs resently I noticed two things that concern me. First in the unser.log I saw the following:
Is this telling me that apache-ssl isn't there or is something else missing? I believe there is a logical connection from apache-ssl to apache2. What might I do to fix this problem?
The second item I saw was in the spooler_error.log. This is what was reported:
I recently add the sixth disk. Was the disk not properly formatted prior to installing into the box. If so how should that have been performed?
Thanks in advance.
Looking throught the logs resently I noticed two things that concern me. First in the unser.log I saw the following:
RAIDiator: nic.agent: "nice -n 5 /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf" failed to start.
Is this telling me that apache-ssl isn't there or is something else missing? I believe there is a logical connection from apache-ssl to apache2. What might I do to fix this problem?
The second item I saw was in the spooler_error.log. This is what was reported:
WARNING: GPT (GUID Partition Table) detected on '/dev/sdf'! The util sfdisk doesn't support GPT. Use GNU Parted.
Warning: The partition table looks like it was made
for C/H/S=*/256/63 (instead of 60801/255/63).
For this listing I'll assume that geometry.
I recently add the sixth disk. Was the disk not properly formatted prior to installing into the box. If so how should that have been performed?
Thanks in advance.
6 Replies
Replies have been turned off for this discussion
Are you seeing this more than once? Is the date recent? I'm not seeing this in my logs.JosephAE wrote: Looking throught the logs resently I noticed two things that concern me. First in the unser.log I saw the following:
RAIDiator: nic.agent: "nice -n 5 /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf" failed to start.
Is this telling me that apache-ssl isn't there or is something else missing? I believe there is a logical connection from apache-ssl to apache2. What might I do to fix this problem?
I see this error on all my disks (which are all 3 TB, so they are GPT formatted). I don't think its a real problem, (assuming RAIDiator reports your volume status as redundant).JosephAE wrote: The second item I saw was in the spooler_error.log. This is what was reported: WARNING: GPT (GUID Partition Table) detected on '/dev/sdf'! The util sfdisk doesn't support GPT. Use GNU Parted.
Warning: The partition table looks like it was made
for C/H/S=*/256/63 (instead of 60801/255/63).
For this listing I'll assume that geometry.
I recently add the sixth disk. Was the disk not properly formatted prior to installing into the box. If so how should that have been performed?
The pro will reformat the drive when you insert it (and generally it is best if you hot-insert the new drive unformatted).- For the Apache-ssl problem: Yes, I see this numerous times in the log and they are resent. I believe that Apache-ssl is a call start Apache2, which is a web server. So does this application allow me to HTTP communicate with my NAS?
:?
For the GPT Warning: I turned off the NAS and then removed the sixth disk. Power up the NAS and did a hot insert of the disk. It is now recovering. I'll see if this corrects the format of the disk when it is finished.
:) - I think the GPT warning is not a problem - so if it still happens after the resync, just leave well enough alone. I've replaced disks with no issues, so it is just advisory info from Parted.
I use https with frontview, and am not seeing the apache-ssl error. Apache is used to power frontview, http share browsing, and several add-ons. So I think you do need to follow up on that one. - The "GPT Warning" didn't clear up after the hot insert. Isn't this error happening because I my disk isn't formatted correctly. I've read somewhere that a disks that uses the GPT partitioning scheme will generate this error when fsdisk is ran. I'm assuming that my other five disks have been formatted with a different partitioning scheme. Because my disk is only 500GB and not a larger size I don't need to use GPT. Do I need to use something else like MBR and if so how would I go about doing that?
Let me try again.JosephAE wrote: The "GPT Warning" didn't clear up after the hot insert. Isn't this error happening because I my disk isn't formatted correctly. I've read somewhere that a disks that uses the GPT partitioning scheme will generate this error when fsdisk is ran. I'm assuming that my other five disks have been formatted with a different partitioning scheme. Because my disk is only 500GB and not a larger size I don't need to use GPT. Do I need to use something else like MBR and if so how would I go about doing that?
Nothing is wrong here. You don't need to do anything about this at all.- On 4.2.16 and later we use GPT for all disks.
I agree with StephenB. Nothing is wrong here.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
