Home › Comunidade Brasileira Endian Firewall › Endian Firewall › Endian Firewall – Suporte › Problemas na inicialização
- Este tópico contém 1 resposta, 2 vozes e foi atualizado pela última vez 13 anos, 8 meses atrás por Bruno Vicente.
-
AutorPosts
-
-
agosto 19, 2010 às 5:01 pm #518rocarvablackParticipante
Boa tarde, estava olhando os logs e olhei o log startup.log, mas ele tem dois FAILED isso é normal ? Estou tentando monitorar o proxy para ver os sites que as pessoas estão acessando mas não consigo. Voê pode me ajudar? Obrigado PS o endian funciona com 4 placas PCI??
Setting hostname
Loading /usr/share/kbd/keymaps/i386/qwerty/us.map.gz
Clearing old files
Setting the clocksource to PIT
Setting the clock
syslog-ng is stopped
Starting syslog-ng: [ OK ]
Starting ulogd: [FAILED]
Setting locale
Setting consolefonts
Initializing Power Management
Setting kernel settings
Setting up loopback
Loading MASQ helper modules
Destroying virtual interfaces… grep: /proc/net/vlan/config: No such file or directory
[ OK ]
Stopping bonding devices [ OK ]
* Updating network card configuration
* Number of NICs found: 3
> Device: eth0 ()
Businfo: 00:09.0
Model: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
Driver: r8169 2.3LK-NAPI
> Device: eth1 ()
Businfo: 00:0b.0
Model: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
Driver: r8169 2.3LK-NAPI
> Device: eth2 ()
Businfo: 00:12.0
Model: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
Driver: via-rhine 1.4.3
* Setting up network interfaces
Start creating virtual interfaces…
Ended creating virtual interfaces… [ OK ]
Starting the CAPI 2.0 daemon: [FAILED]
Bringing network up
Starting monit: [ OK ]
Starting QoS
2010-08-12 12:38:17,286 – restartqos.py[3213] – INFO – Loading configuration
2010-08-12 12:38:20,148 – restartqos.py[3213] – INFO – Setting QOS of device: eth1 [UPLOAD=2000, DOWNLOAD=2000]
2010-08-12 12:38:40,609 – restartqos.py[3213] – INFO – Setting QOS of device: eth2 [UPLOAD=2000, DOWNLOAD=2000]
/etc/rc.d/start/39firewall: line 3: loadconf: command not found
Setting up firewall rules
/etc/firewall/hooks/00ipac:
Couldn’t load target `standard’:/lib/iptables/libipt_standard.so: cannot open shared object file: No such file or directory
run-parts: /etc/firewall/hooks/00ipac exited with return code 2
Starting uplinksdaemon at boot time: [ OK ]
Starting collectd:
Stopping dnsmasq: [ OK ]
dnsmasq is stopped
Starting dnsmasq: [ OK ]
Starting emi: [ OK ]
Setting up ip accounting
Couldn’t load target `standard’:/lib/iptables/libipt_standard.so: cannot open shared object file: No such file or directory
2010-08-12 12:41:38,405 – createtemplates.py[5942] – INFO – Creating message templates for service “dansguardian”
2010-08-12 12:41:39,965 – createtemplates.py[5942] – INFO – Creating message templates for service “postfix”
2010-08-12 12:41:41,488 – createtemplates.py[5942] – INFO – Creating message templates for service “amavisd-new”
2010-08-12 12:41:48,531 – createtemplates.py[5942] – INFO – Creating message templates for service “havp”
2010-08-12 12:41:58,253 – createtemplates.py[5942] – INFO – Creating message templates for service “logsurfer”
2010-08-12 12:42:21,119 – createtemplates.py[5942] – INFO – Creating message templates for service “p3scan”
2010-08-12 12:42:21,899 – createtemplates.py[5942] – INFO – Creating message templates for service “squid”
2010-08-12 12:42:44,863 – createtemplates.py[5942] – INFO – Creating message templates for service “backup”
ipsec_setup: Stopping Openswan IPsec…
ipsec_setup: stop ordered, but IPsec appears to be already stopped!
ipsec_setup: doing cleanup anyway…
IPsec stopped
ipsec_setup: Starting Openswan IPsec 2.6.24…
ipsec_setup: br2: error fetching interface information: Device not found
ipsec_setup: unable to determine address of `br2′
2010-08-12 12:43:56,014 – restartsmtpscan.py[6826] – INFO – commtouch is not installed
clamd (pid 4264) is running…
sed: can’t read /var/efw//smtpscan/settings: No such file or directory
sed: can’t read /var/efw//smtpscan/settings: No such file or directory
PURPLE: tap0
Starting Snort (if enabled)
2010-08-12 12:44:57,059 – restartsquid.py[7138] – INFO – Reading squid settings…
2010-08-12 12:44:58,215 – restartsquid.py[7138] – INFO – Writing squid configuration…
/usr/lib/python2.4/site-packages/Cheetah/Compiler.py:1578: UserWarning: You supplied an empty string for the source!
2010-08-12 12:45:14,420 – restartsquid.py[7138] – INFO – Reloading Authentication…
dnsmasq (pid 7463 6014) is running…
2010-08-12 12:45:34,184 – restartsquid.py[7138] – INFO – Reloading squid…
PURPLE: tap0
2010-08-12 12:45:58,357 – restarthavp.py[7991] – INFO – Reading HAVP settings…
clamd (pid 4264) is running…
2010-08-12 12:46:05,584 – restarthavp.py[7991] – INFO – Writing havp configuration…
2010-08-12 12:46:06,299 – restarthavp.py[7991] – INFO – Stopping havp…
havp (pid 4263 4262 4261 4260 4259 4258 4257 4256 4255 4254 4253 4252 4251 4250 4249 4248 4247 4246 4245 4244 4243 4242 4241 4240 4239 4238 4237 4236 4235 4234 4233 4232 4231 4230 4229 4228 4227 4226 4225 4223 4221) is running…
Shutting down HTTP virus scanner (havp): [ OK ]
havp is stopped
2010-08-12 12:46:07,925 – restarthavp.py[7991] – INFO – Starting havp…
Starting HTTP virus scanner (havp): [ OK ]
2010-08-12 12:46:34,292 – restartdansguardian.py[8103] – INFO – Writing dansguardian configuration…
2010-08-12 12:46:34,939 – restartdansguardian.py[8103] – INFO – Stopping dansguardian…
2010-08-12 12:46:37,587 – restartsarg.py[8119] – INFO – Reading Sarg settings…
2010-08-12 12:46:37,959 – restartsarg.py[8119] – INFO – Writing Sarg configuration…
Starting snmpd: [ OK ]
Installing crontab
Shutting down fcron [ OK ]
Starting fcron: [ OK ]
Wireguard_webadmin
Sistema gratuito (Open Source) para gestão de VPN's WireGuard com uma Web interface intuitiva e fácil de usar.
Principais funcionalidades:
- Sistema de Firewall completo e flexível.
- Encaminhamento de portas
- Suporte a multi usuário com níveis diferentes de acesso
- Múltiplas instâncias do Wireguard
- Crypto key routing para configuração de VPN site-to-site
O projeto é Open Source, fácil de instalar e está disponível em wireguard_webadmin
-
agosto 20, 2010 às 8:04 pm #5776Bruno VicenteParticipante
Rocarvablack,
A principio existem duas formas de você verificar os logs do proxy no Endian.
1 – Através da interface web no Menu Históricos > Proxy Web, ou no próprio Dasboard em Serviços Live Log.
2 – No console, aí geralmente uso o comando #tail -F /var/log/squid/access.log
Lembrando que, para conseguir visualizar os logs do proxy, a opção deverá ser ativa no Menu Proxy > Configurações do Histórico > HTTP proxy logging / Enable logging [check].
Quanto as falhas na inicialização, o ULOG na versão 2.4 está com BUG e o sistema de logs de firewall não funciona.
Pesquise no fórum sobre como fazer o upgrade do Endian e corrigir esta falha.
Sobre CAPI 2.0, não sei o que pode ser.
-
-
AutorPosts
- O tópico ‘Problemas na inicialização’ está fechado para novas respostas.