Dopo aver eliminato un gran numero di istantanee (circa 1500), la GUI di FreeNAS 9.3 visualizza "Un errore accaduto". Dopo due giorni

La mia GUI FreeNAS 9.3 è schiacciata dopo aver eliminato un gran numero di istantanee (circa 1500)

E ora, Mostra solo queste parole:

An error occurred. Sorry, the page you are looking for is currently unavailable. Please try again later. If you are the system administrator of this resource then you should check the error log for details. Faithfully yours, nginx. 

Ho provato a eseguire il command "# nginx restart di servizio", ma non ho usato.


Altre informazioni seguenti:

※ Utilizza il command "cat /var/log/nginx-error.log": (Il mio URL Web FreeNAS è http://192.168.168.168/ )

 2015/07/20 09:59:24 [error] 57959#0: *1 upstream prematurely closed connection while reading response header from upstream, client: 192.168.168.200, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.168.168" 2015/07/20 09:59:25 [error] 57959#0: *1 upstream prematurely closed connection while reading response header from upstream, client: 192.168.168.200, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.168.168", referrer: "http://192.168.168.168/" 2015/07/20 09:59:32 [error] 57959#0: *1 upstream prematurely closed connection while reading response header from upstream, client: 192.168.168.200, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.168.168" 2015/07/20 09:59:33 [error] 57959#0: *1 upstream prematurely closed connection while reading response header from upstream, client: 192.168.168.200, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.168.168", referrer: "http://192.168.168.168/" 

Grazie mille!


2015/07/20 Aggiungi: Nel /var/log/messages , contrassegna l'"Errore" solo dopo:

 Jul 20 09:37:00 freenas manage.py: [freenasOS.Configuration:505] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known> Jul 20 09:37:00 freenas kernel: <118>Jul 20 09:37:00 freenas manage.py: [freenasOS.Configuration:505] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known> Jul 20 09:37:04 freenas nmbd[78370]: [2015/07/20 09:37:04.251526, 0] ../source3/nmbd/nmbd_packets.c:1174(process_lanman_packet) Jul 20 09:37:04 freenas nmbd[78370]: process_lanman_packet: Discarding datagram from IP 192.168.168.160. Source name FREENAS<00> is one of our names ! Jul 20 09:37:04 freenas kernel: <118>Jul 20 09:37:04 freenas nmbd[78370]: [2015/07/20 09:37:04.251526, 0] ../source3/nmbd/nmbd_packets.c:1174(process_lanman_packet) Jul 20 09:37:04 freenas kernel: <118>Jul 20 09:37:04 freenas nmbd[78370]: process_lanman_packet: Discarding datagram from IP 192.168.168.160. Source name FREENAS<00> is one of our names ! Jul 20 09:37:12 freenas manage.py: [freenasOS.Configuration:505] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known> Jul 20 09:37:12 freenas kernel: <118>Jul 20 09:37:12 freenas manage.py: [freenasOS.Configuration:505] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known> 

PS: Il mio ospite FreeNAS non può toccare Internet.


2015/07/20 Aggiunta: Ho trovato questa pagina per risolvere il mio problema: FreeNAS Web UI non risponde

e faccio i seguenti passi per risolvere questa domanda:

Passo 1: Esegui ps auxwww | grep freenas command ps auxwww | grep freenas

Fase 2: trovare il risultato come root 3118 0.0 0.4 557616 140848 ?? I 25Jun15 45:41.21 /usr/local/bin/python -R /usr/local/www/freenasUI/manage.py runfcgi method=threaded host=127.0.0.1 port=9042 pidfile=/var/run/django.pid (python2.7) root 3118 0.0 0.4 557616 140848 ?? I 25Jun15 45:41.21 /usr/local/bin/python -R /usr/local/www/freenasUI/manage.py runfcgi method=threaded host=127.0.0.1 port=9042 pidfile=/var/run/django.pid (python2.7)

In questo caso, il PID è 3118

Fase 3: Esegui kill -15 3118 per uccidere il process

Fase 4: eseguire ps auxwww | grep freenas ps auxwww | grep freenas per controllare il process 3118 è già ucciso. Se no, Run kill -9 3118 per forzare uccidere questo process.

Passo 5: Esegui service django start per avviare il process django. Fatto!


Ma, ancora non so come il sito si schiacci dopo aver eliminato molte istantanee …

Grazie!

Suggerimenti per Linux e Windows Server, quali Ubuntu, Centos, Apache, Nginx, Debian e argomenti di rete.