|
|
|
|
||||||
| alt.apache.configuration Apache web server configuration issues. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
This weekend we had an odd occurrence where many of our servers
stopped responding. SSH wouldn't connect, and when you physicall went to the console for that server you were presented with this: bash ~# None of the commands worked. The first server I found like this, I tried to reboot and it gave me a grub 15 error. Our Apache webserver is having the same issues, and my feeling is that once we reboot, it will give me the same error. For right now, it is running, we just can't get in to make any changes. Our backup server is in the same shape, so we can't pull from the backup. The question I have, is what are the options for pulling any files or configurations off that machine? It is still running, we just can't get into it. None of the sites we host are particularly advanced, so we could probably just go to each site in a webbrowser and save each page. That would at least save the website data for us. I didn't know if anyone know of any tools or scripts that could crawler a website and download all the data. |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
"Jerim" <wyount@gmail.com> wrote in message
news:3a754790-e5bd-4dea-909e-c37741d213f0@e4g2000hsg.googlegroups.com... > The question I have, is what are the options for pulling any files or > configurations off that machine? It is still running, we just can't > get into it. None of the sites we host are particularly advanced, so > we could probably just go to each site in a webbrowser and save each > page. That would at least save the website data for us. I didn't know > if anyone know of any tools or scripts that could crawler a website > and download all the data. > If you just want to trawl all the pages on the site and download them all then you could try 'wget' |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 Jerim wrote: > The question I have, is what are the options for pulling any files or > configurations off that machine? It is still running, we just can't > get into it. None of the sites we host are particularly advanced, so > we could probably just go to each site in a webbrowser and save each > page. That would at least save the website data for us. I didn't know > if anyone know of any tools or scripts that could crawler a website > and download all the data. > > I would power off, remove the HDD and put it into another machine (if possible). If the server is still running then the chance of physical HDD damage is probably pretty low. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFHqewNuv4tpb9qDZQRAiB3AKCVcao5S71ctHLep2rALW uvS/DxcwCfat2k 0btBqkkR0O+qlGquixxLpkI= =2BPY -----END PGP SIGNATURE----- |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
Jerim wrote:
> This weekend we had an odd occurrence where many of our servers > stopped responding. SSH wouldn't connect, and when you physicall went > to the console for that server you were presented with this: > > bash ~# > > None of the commands worked. The first server I found like this, I > tried to reboot and it gave me a grub 15 error. Our Apache webserver > is having the same issues, and my feeling is that once we reboot, it > will give me the same error. For right now, it is running, we just > can't get in to make any changes. Our backup server is in the same > shape, so we can't pull from the backup. > > The question I have, is what are the options for pulling any files or > configurations off that machine? It is still running, we just can't > get into it. None of the sites we host are particularly advanced, so > we could probably just go to each site in a webbrowser and save each > page. That would at least save the website data for us. I didn't know > if anyone know of any tools or scripts that could crawler a website > and download all the data. > > It sounds to me like you had a brown out or some sort of power fluctuation and perhaps have a borked file. Usually the error 15 is caused when the boot loader can not find and/or read the vmlinuz file in the /boot directory |
|
![]() |
| Outils de la discussion | |
|
|