Logrotate Failed on Boot

giomke · January 23, 2023, 5:15pm

Hi guys.

Log rotate failed on boot.
How I can fix this?

Jan 23 21:01:03 fedora systemd[1]: Starting logrotate.service - Rotate log files...
Jan 23 21:01:03 fedora logrotate[1208]: error: stat of /var/log/boot.log failed: Permission denied
Jan 23 21:01:03 fedora systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Jan 23 21:01:03 fedora systemd[1]: logrotate.service: Failed with result 'exit-code'.
Jan 23 21:01:03 fedora systemd[1]: Failed to start logrotate.service - Rotate log files.

glb · January 23, 2023, 5:25pm

Fix the permissions? It could be an SELinux permissions problem. Does the following command show any output?

sudo restorecon -r -v /var/log

computersavvy · January 23, 2023, 7:15pm

There was definitely an selinux policy update in the last couple days that may have contributed to that error.

giomke · January 28, 2023, 6:03am

Fixed itself

rihcaro · April 4, 2023, 4:03pm

Hello Gregory! I found this post because I googled the term “registration fee service”. This term no longer appears as a boot failure.

The first time I pasted this command line, the response came out immediately with no result, just my username appearing on the line below.

Now I repeat the procedure and nothing comes out, there is no response and the boot is different. That is, when restarting, the machine remains on (sometimes it turns off), and the monitor turns off, turns on again with an all black background, only with a character (hyphen) in the middle of the screen and only after that does the next screen appear with the Fedora Linux versions installed.

Is there anything I can do about it?

Have a nice day and thank you for your attention.

Texto original

Olá Gregório! Encontrei este post porque pesquisei no Google o termo “serviço de taxa de registro”. Este termo não aparece mais como uma falha de inicialização.

A primeira vez que colei esta linha de comando, a resposta saiu imediatamente sem resultado, apenas meu nome de usuário aparecendo na linha abaixo.

Agora repito o procedimento e não sai nada, não há resposta e a inicialização é diferente. Ou seja, ao reiniciar, a máquina permanece ligada (às vezes desliga), e o monitor desliga, liga novamente com fundo todo preto, apenas com um caractere (hífen) no meio da tela e só depois disso é que a tela seguinte aparece com as versões do atenção.Fedora Linux instaladas.

Há algo que eu possa fazer sobre isso?

Tenha um bom dia e obrigado pela atenção.

glb · April 4, 2023, 4:26pm

It sounds like a problem with graphical boot (plymouth).

Maybe these commands would fix it?

$ sudo dnf install plymouth-theme-spinner
$ sudo plymouth-set-default-theme spinner -R

rihcaro · April 4, 2023, 4:51pm

Command line error: argument -R/–randomwait: expected one argument
[ricardopinto@localhost ~]$ sudo dnf install plymouth-theme-spinner sudo plymouth-set-default-theme spinner -R
usage: dnf [-c [config file]] [-q] [-v] [–version] [–installroot [path]]
[–nodocs] [–noplugins] [–enableplugin [plugin]]
[–disableplugin [plugin]] [–releasever RELEASEVER]
[–setopt SETOPTS] [–skip-broken] [-h] [–allowerasing]
[-b | --nobest] [-C] [-R [minutes]] [-d [debug level]]
[–debugsolver] [–showduplicates] [-e ERRORLEVEL] [–obsoletes]
[–rpmverbosity [debug level name]] [-y] [–assumption]
[–enablerepo [repo]] [–disablerepo [repo] | --repo [repo]]
[–enable | --disable] [-x [package]] [–disableexcludes [repo]]
[–repofrompath [repo,path]] [–noautoremove] [–nogpgcheck]
[–color COLOR] [–refresh] [-4] [-6] [–destdir DESTDIR]
[–downloadonly] [–comment COMMENT] [–bugfix] [–enhancement]
[–newpackage] [–security] [–advisory ADVISORY] [–bz BUGZILLA]
[–cve CVES] [–sec-severity {Critical,Important,Moderate,Low}]
[–forcearch ARCH]
Command line error: argument -R/–randomwait: expected one argument
[ricardopinto@localhost ~]$

Please tell me what do I do? Thanks.

glb · April 4, 2023, 4:52pm

That was meant to be two separate commands.

rihcaro · April 4, 2023, 5:12pm

Please excuse my inattention. I saw a line and didn’t realize it was two commands.

Here are the results:

Please excuse my inattention. I saw a line and didn’t realize it was two commands.
Here are the results:
sudo dnf install plymouth-theme-spinner

[ricardopinto@localhost ~]$ sudo dnf install plymouth-theme-spinner
[sudo] password for ricardopinto:
I’m sorry, please try again.
[sudo] password for ricardopinto:
Last metadata check: 1:44:06 ago on Tue Apr 04, 2023 12:17:10.
The plymouth-theme-spinner-22.02.122-3.fc37.x86_64 package is already installed.
Resolved dependencies.
Nothing to do.
Concluded!
[ricardopinto@localhost ~]$

sudo plymouth-set-default-theme spinner -R
[ricardopinto@localhost ~]$

glb · April 4, 2023, 5:13pm

It looks like it worked. Does the system boot properly now?

rihcaro · April 4, 2023, 5:37pm

Yes, the results of the commands were satisfactory but the situation remains the same, that is, it did not correct this situation.

I’d like to say another way about the (error) on startup that I couldn’t say because I hadn’t even noticed this hypothesis before:

the brief shutdown of the monitor during the reboot is a kind of mask to prevent access to the Bios. It is exactly during this moment when the screen with the manufacturer’s logo should appear to access the Bios or not that the monitor turns off and turns on again with a black background and a hyphen. Another thing I would like to report, including I had already raised this subject with Ben Cotton but I believe I have not been able to express myself correctly but what also happens is that even before this abnormal reboot, when I could still access the Bios, I corrected the time that always appears three hours in advance and when I open the system a message appears saying that the time has been updated.

That’s another matter.

I don’t know if I’m making a mistake by mentioning more than one occurrence at a time.

Thank you and waiting for you.

TEXTO ORIGINAL (ORIGINAL TEXT)

Sim, os resultados dos comandos foram satisfatórios mas a situação continua igual, ou seja, não corrigiu essa situação.

Eu gostaria de dizer de outra forma sobre o (erro) na inicialização que eu não soube dizer porque nem havia percebido essa hipótese antes:

o breve desligamento do monitor durante a reinicialização é uma espécie de máscara para impedir o acesso a Bios. É exatamente durante esse momento em que deveria aparecer a tela com o logo da marca do fabricante para acessar ou não a Bios que o monitor desliga e volta a ligar com um fundo preto e um hífen. Outra coisa que eu gostaria de relatar, inclusive eu já havia levantado esse assunto com o Ben Cotton mas acredito que eu não tenha conseguido me expressar corretamente mas o que também acontece é qe mesmo antes desta reinicialização anormal, quando eu ainda conseguia acessar a Bios, eu corrigia o horário que sempre aparece três horas adiantado e quando eu quando abre o sistema está aparecendo uma mensagem dizendo que o horário foi atualizado.

Isso é outro assunto.

Não sei se estou fazendo confusão em mencionar mais de uma ocorrência por vez.

Obrigado e no seu aguardo.

glb · April 4, 2023, 5:49pm

It might be related. There are settings in the BIOS menus to disable showing the “post” messages. It sounds like you might have changed that setting when you corrected the time. The BIOS setting can be labeled differently depending on the system manufacturer. It might be labeled something like “fast boot” or “quiet boot”. To get back into your BIOS to change the setting back, you will have to hold a special key. Which key to hold is also different depending on your system manufacturer. It is usually one of Esc, F1, F2, or Del. I think most manufacturers use F2 these days. You have to be fast. Press the key immediately after turning on your system. If it doesn’t work, try again or try again with another key. If you can find and turn off the “fast boot”, then I think you will see the startup messages you are missing.

rihcaro · April 4, 2023, 8:47pm

Hello again and I apologize for the delay in responding but I am facing a problem that does not allow me to remain online. I hope you understand me. I understand what you’re saying, but that’s not the case.

Regardless of the boot method, which in this case I selected the quick way, some Bios screen, either with the full logo or with reduced information, something appears allowing you to use the access key and explicit saying that from yesterday to today nothing from the BIOS appears and yes this black background overlay with apparent cut of monitor power.

Remember that I commented on the issue of time (hours, minutes and seconds) that, even if I modify it by delaying three hours for the time zone in Brazil, there is a change that occurs remotely that I have no idea how this is done, nor of this mask created during the short BIOS display time.

I don’t know how to solve it and I’m waiting for your help.

Thank you very much.

Best regards,

Ricardo Pinto.

TEXTO ORIGINAL

Olá novamente e peço desculpas pela demora em responder mas estou enfrentando um problema que não me permite permanecer online. Eu espero que você me entenda. Eu entendo o que você está dizendo, mas não é o caso.

Independente do método de boot, que no caso selecionei da forma rápida, alguma tela da Bios, seja com logo completo ou com informações reduzidas, aparece algo permitindo usar a chave de acesso e explícito dizendo que de ontem para hoje simplesmente NADA da BIOS aparece e sim esta sobreposição de fundo preto com aparente corte da energia do monitor.

Lembre-se que comentei sobre a questão do horário (horas, minutos e segundos) que, mesmo que eu modifique atrasando três horas para o fuso horário do Brasil, há uma mudança que ocorre remotamente que não faço ideia de como isso é feito, nem dessa máscara criada durante o pouco tempo de exibição do BIOS.

Não sei como resolver e aguardo sua ajuda.

Muito obrigado.

Com os melhores cumprimentos,

Ricardo Pinto.

glb · April 4, 2023, 9:30pm

I saw a bug report recently about video not initializing correctly for some systems. It is here:

https://bugzilla.redhat.com/show_bug.cgi?id=2176782

None of my computers are affected by it. But maybe yours is? You might try adding vga=791 to your kernel parameters and see if that fixes the problem you are seeing.

Unfortunately, editing the kernel command line can be tricky. There are some directions here.

glb · April 4, 2023, 9:38pm

You probably need to run this command (or something similar).

$ sudo timedatectl set-timezone America/Sao_Paulo

You can verify that the settings are correct by running timedatectl without any parameters.

[/home/gregory]$ timedatectl 
               Local time: Tue 2023-04-04 18:32:43 -03
           Universal time: Tue 2023-04-04 21:32:43 UTC
                 RTC time: Tue 2023-04-04 21:32:42
                Time zone: America/Sao_Paulo (-03, -0300)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

It is normal for the BIOS (aka, “RTC”) to be in UTC time. If you really don’t want that, the following command might work.

$ sudo timedatectl set-local-rtc 1

glb · April 4, 2023, 9:53pm

If you are saying that the BIOS doesn’t show at all during boot (nada). But then the video works properly after Fedora Linux loads, I have a friend whose computer did something like that recently. In his case, he had to use a different video output to see the BIOS post screen. If I recall correctly, I think he was using a nVidia card and he had to use the HDMI output to see the initial boot screen. I think that was a problem with the video card and I don’t know if he ever solved it. I could ask him though.

rihcaro · April 4, 2023, 11:15pm

Yes, the video works correctly after Fedora Linux loads.
I use a basic PC, video connected by VGA cable.

rihcaro · April 4, 2023, 11:27pm

I tried the command and it got no response but as is normal there is no reason to change anything about it.

[ricardopinto@localhost ~]$ sudo timedatectl set-timezone America/Sao_Paulo
[sudo] senha para ricardopinto:
[ricardopinto@localhost ~]$ sudo timedatectl set-timezone America/Sao_Paulo
[ricardopinto@localhost ~]$ timedatectl
Local time: ter 2023-04-04 20:22:38 -03
Universal time: ter 2023-04-04 23:22:38 UTC
RTC time: ter 2023-04-04 23:22:38
Time zone: America/Sao_Paulo (-03, -0300)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
[ricardopinto@localhost ~]$ sudo timedatectl set-local-rtc 1
[ricardopinto@localhost ~]$ sudo timedatectl set-local-rtc 1
[ricardopinto@localhost ~]$

glb · April 4, 2023, 11:29pm

Some BIOS’s have a setting to force the video output to use either the internal (onboard) video card or an add-in card. Is that setting correct?

glb · April 4, 2023, 11:31pm

If you run timedatectl again, I bet the last line has changed to RTC in local TZ: yes. Consequently, your BIOS should no longer be off by 3 hours.