journactl apresentando vários erros - log.

phk
(usa Ubuntu)

Enviado em 06/01/2019 - 12:09h

Oi pessoal. Eu estou com o boot muito lento, então resolvi pesquisar o motivo. Os erros estão aqui. Quero uma orientação para resolvê-los. Estou pesquisando na net para saber como resolver. Obrigado.
jan 05 20:22:20 phk kernel: ip_local_port_range: prefer different parity for start/end values.
jan 05 20:22:20 phk kernel: kvm: disabled by bios
jan 05 20:22:01 phk systemd-sysctl[437]: Line is not an assignment at '/etc/sysctl.d/99-sysctl.conf:178': (null)
jan 05 20:22:10 phk systemd[1]: Failed to start Apply Kernel Variables.
jan 05 20:22:16 phk systemd-sysctl[1437]: Line is not an assignment at '/etc/sysctl.d/99-sysctl.conf:178': (null)
jan 05 20:22:28 phk systemd-sysctl[1604]: Line is not an assignment at '/etc/sysctl.d/99-sysctl.conf:178': (null)
jan 05 20:23:28 phk systemd[1]: Timed out waiting for device dev-zram0.device.
jan 05 20:23:37 phk avahi-daemon[1982]: open("/services/phpmyadmin.service", O_RDONLY): No such file or directory
jan 05 20:23:37 phk avahi-daemon[1982]: Failed to load service group file /services/phpmyadmin.service, ignoring.
jan 05 20:24:16 phk wpa_supplicant[2231]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
jan 05 20:24:16 phk wpa_supplicant[2231]: dbus: Failed to construct signal
jan 05 20:24:18 phk systemd[1]: Failed to start Starts and stops the Apache Server.
jan 05 20:24:22 phk systemd[1]: Failed to start MySQL Community Server.
jan 05 20:24:22 phk systemd[1]: Failed to start MySQL Community Server.
jan 05 20:24:22 phk systemd[1]: Failed to start MySQL Community Server.
jan 05 20:24:23 phk systemd[1]: Failed to start MySQL Community Server.
jan 05 20:24:23 phk systemd[1]: Failed to start MySQL Community Server.
jan 05 20:24:23 phk systemd[1]: Failed to start MySQL Community Server.
jan 05 20:24:23 phk rsyslogd[1977]: file '/var/log/arno-iptables-firewall': open error: Permission denied [v8.32.0 try http://www.rsyslog.com/e/2433 ]
jan 05 20:24:23 phk systemd[1]: Failed to start MySQL Community Server.
jan 05 20:24:25 phk systemd[3253]: rc-local.service: Failed to execute command: Exec format error
jan 05 20:24:25 phk systemd[3253]: rc-local.service: Failed at step EXEC spawning /etc/rc.local: Exec format error
jan 05 20:24:26 phk systemd[1]: Failed to start /etc/rc.local Compatibility.
jan 05 20:24:40 phk systemd[1]: Failed to start LSB: Starts and stops AVG Anti-Virus daemon.
jan 05 20:25:50 phk systemd-sysctl[7621]: Line is not an assignment at '/etc/sysctl.d/99-sysctl.conf:178': (null)
jan 05 20:25:57 phk lightdm[7839]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
jan 05 20:25:57 phk lightdm[7839]: PAM adding faulty module: pam_kwallet.so
jan 05 20:25:57 phk lightdm[7839]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
jan 05 20:25:57 phk lightdm[7839]: PAM adding faulty module: pam_kwallet5.so
jan 05 20:26:46 phk lightdm[9846]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
jan 05 20:26:46 phk lightdm[9846]: PAM adding faulty module: pam_kwallet.so
jan 05 20:26:46 phk lightdm[9846]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
jan 05 20:26:46 phk lightdm[9846]: PAM adding faulty module: pam_kwallet5.so
jan 05 20:28:55 phk rsyslogd[1977]: file '/var/log/arno-iptables-firewall': open error: Permission denied [v8.32.0 try http://www.rsyslog.com/e/2433 ]
jan 05 20:30:51 phk colord-sane[19479]: io/hpmud/pp.c 627: unable to read device-id ret=-1
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: read error
jan 05 21:15:49 phk rngd[40567]: No entropy sources working, exiting rngd

meu rc.local. Não sei o que tem de errado nele.
sudo mkdir -p /dev/cgroup/cpu
sudo mount -t cgroup cgroup /dev/cgroup/cpu -o cpu
sudo mkdir -m 0777 /dev/cgroup/cpu/user
sudo echo "1" > /dev/cgroup/cpu/user/notify_on_release
sudo echo "/usr/local/sbin/cgroup_clean" > /dev/cgroup/cpu/release_agent
hdparm -W1 -M254 /dev/sdc
hdparm -W1 -M254 /dev/sdb
hdparm -W1 -M254 /dev/sdd
echo 256 > /sys/block/sdc/queue/nr_requests
echo 256 > /sys/block/sdc/queue/read_ahead_kb
echo 256 > /sys/block/sdb/queue/read_ahead_kb
echo 256 > /sys/block/sdd/queue/read_ahead_kb
echo 1 > /proc/sys/vm/overcommit_memory
echo 60 > /proc/sys/vm/overcommit_ratio
echo 10 > /proc/sys/vm/dirty_ratio
echo 5 > /proc/sys/vm/dirty_background_ratio
O journalctl acusou o erro.

Mauriciodez
(usa Debian)

Enviado em 06/01/2019 - 12:32h

.
.
.
.
Eu já tinha respondido e o tópico foi excluído .. qual o motivo de ter aberto outro tópico com o mesmo enredo ???

------------------------------------------| Linux User #621728 |-----------------------------------------

" Nem sempre é amigo aquele que te tira do buraco !!! ( Saddam Hussein )"

------------------------------------------| Linux User #621728 |-----------------------------------------

phk
(usa Ubuntu)

Enviado em 07/01/2019 - 21:11h

Desculpe, mas eu tinha posto o tópico em um fórum errado. Assim removi aquele tópico e coloquei no local certo, porém não vi nenhuma resposta relacionado ao tópico. Obrigado.

BiaMonteiro
(usa Arch Linux)

Enviado em 07/01/2019 - 21:28h

Já tive um problema muito parecido com o seu.
E ele surgiu depois que fiz uma instalação mal feita do Apache, do PHP e do MySQL, com apt install apache* mysql* php* juntamente com a opção servidor web do tasksel do Debian. Instalou-se meio mundo de pacotes e acabou dando problema no apacheds.service.

Sabe como resolvi esse problema?
Desinstalei todos os pacotes, juntamente com os aplicativos de configuração, com apt purge apache* mysql* php* e removendo a opção web do tasksel. Logo em seguida, fui nos diretórios do systemd e fui deletando os serviços problemáticos um por um em locais como /etc/systemd/system e /lib/systemd/system. Depois o problema foi consertado e refiz uma instalação, dessa vez bem feita, dos serviços.

Essa minha experiência é para ilustrar uma coisa:
esses erros que você vem enfrentando surgiram devido a alguma má configuração que você fez no computador.
Por isso, pergunto: essas mensagens do systemd começaram a aparecer depois de qual evento que você fez no computador?

Mauriciodez
(usa Debian)

Enviado em 07/01/2019 - 21:37h

entendo .. vamos recomeçar então .

Olha só ... só através desse log não tem como identificar o que é responsável pelo estrago, então a principio faça o seguinte, desabilite tudo que possa ser desnecessário , mysql, phpmyadmin, iptables, etc ... principalmente o AVG.

Caso os erro cessem a gente passa a averiguar qual serviço é o responsável pela lambança.


NOTA: caso identifique um padrão como a Beatriz sugeriu, não é uma de desinstalar de cara, desabilite o serviço antes para ter certeza

------------------------------------------| Linux User #621728 |-----------------------------------------

" Nem sempre é amigo aquele que te tira do buraco !!! ( Saddam Hussein )"

------------------------------------------| Linux User #621728 |-----------------------------------------

BiaMonteiro
(usa Arch Linux)

Enviado em 07/01/2019 - 21:45h

Dois serviços que recomendo não desinstalar são o Avahi e o Dbus. São essenciais no sistema.

phk
(usa Ubuntu)

Enviado em 10/01/2019 - 10:52h

Obrigado pela resposta. Vou executar os procedimentos e retornar o resultado. Muito obrigado mesmo.