Re: I'm getting "recovering journal" when rebooting after pulling and reconfiguring my system

[Oleander via]

Hi Marek,
I don't, only the system one.

Thanks anyway.

 Original Message 
On Sep 13, 2024, 15:40, Marek Paśnikowski wrote:

> Oleander via  writes: > This only happens with Sway and only after 
> reconfiguring the system. I > did a test with Gnome and the system boots just 
> fine. Any Sway user > experiencing the same? > Do you have any mount points 
> other that the system ones? The only scenario that I can think of is that 
> Sway on Guix does not unmount partitions cleanly before powering computers 
> down. Besides this thought, I will not be able to help any more, as I use a 
> configuration vastly different from yours.

Re: I'm getting "recovering journal" when rebooting after pulling and reconfiguring my system

[Ignas Lapėnas]

Sway user here. I have the same issue. Using ext4 as my filesystem. Also
the same happens during powerloss.

Oleander via  writes:

> This only happens with Sway and only after reconfiguring the system. I
> did a test with Gnome and the system boots just fine. Any Sway user
> experiencing the same?
>
> Thank you!
>  Original Message 
> On Sep 11, 2024, 11:40, Oleander wrote:
>
>> System boots just fine even if I get the "recovering journal" message. The 
>> smartctl test on my device passes.
>>
>> I don't get the message if the previous session guix pull or guix system 
>> reconfigure are not run.
>>
>> I shutdown/reboot my system with loginctl poweroff/reboot. With sudo 
>> shutdown/reboot I get the same behavior.
>>
>> Any hint?
>>
>> Thank you!

-- 
Pagarbiai,
Ignas Lapėnas

Re: I'm getting "recovering journal" when rebooting after pulling and reconfiguring my system

[Marek Paśnikowski]

Oleander via  writes:

> This only happens with Sway and only after reconfiguring the system. I
> did a test with Gnome and the system boots just fine. Any Sway user
> experiencing the same?
>

Do you have any mount points other that the system ones?  The only
scenario that I can think of is that Sway on Guix does not unmount
partitions cleanly before powering computers down.

Besides this thought, I will not be able to help any more, as I use a
configuration vastly different from yours.

Re: I'm getting "recovering journal" when rebooting after pulling and reconfiguring my system

[Oleander via]

This only happens with Sway and only after reconfiguring the system. I did a 
test with Gnome and the system boots just fine. Any Sway user experiencing the 
same?

Thank you!
 Original Message 
On Sep 11, 2024, 11:40, Oleander wrote:

> System boots just fine even if I get the "recovering journal" message. The 
> smartctl test on my device passes.
>
> I don't get the message if the previous session guix pull or guix system 
> reconfigure are not run.
>
> I shutdown/reboot my system with loginctl poweroff/reboot. With sudo 
> shutdown/reboot I get the same behavior.
>
> Any hint?
>
> Thank you!

I'm getting "recovering journal" when rebooting after pulling and reconfiguring my system

[Oleander via]

System boots just fine even if I get the "recovering journal" message. The 
smartctl test on my device passes.

I don't get the message if the previous session guix pull or guix system 
reconfigure are not run.

I shutdown/reboot my system with loginctl poweroff/reboot. With sudo 
shutdown/reboot I get the same behavior.

Any hint?

Thank you!

Re: Restart freezes after reconfiguring system

[Felix Lechner via]

Hi Georgios,

On Sun, Jul 2, 2023 at 6:50 AM Georgios Athanasiou  wrote:
>
> After running `guix system reconfigure' and then trying to restart my
> computer, it won't restart.  I get a blank screen with the cursor
> blinking at the top left corner, the computer not responding anymore.

Sometimes, I also have issues restarting but they are generally
unrelated to whether I just reconfigured.

How did you restart? (Did you type "reboot" in a root shell?) How long
did you wait before your patience ran out?

Also, it might be helpful if you could link to your system config.

Thanks for using GNU Guix!

Kind regards
Felix

Restart freezes after reconfiguring system

[Georgios Athanasiou]

Hello Guix!

I've been trying out Guix OS since about a week now.  It's been very

nice so far, though I do have a slight problem.

After running `guix system reconfigure' and then trying to restart my

computer, it won't restart.  I get a blank screen with the cursor

blinking at the top left corner, the computer not responding anymore.

I have to reboot by holding down the hardware button on the computer.

After the hard reboot, restart works as expected, until I reconfigure

the system again.

Powering off gives the same result, i.e. the computer freezes instead

of shutting down.  It doesn't matter whether I do it from inside Gnome

or a root console.

Does anyone else have this problem?  Could I manually restart some

service and then have restart work normally?

Thanks!

G.

Restart freezes after reconfiguring system

[Georgios Athanasiou]

Hello Guix!

I've been trying out Guix OS since about a week now.  It's been very
nice so far, though I do have a slight problem.

After running `guix system reconfigure' and then trying to restart my
computer, it won't restart.  I get a blank screen with the cursor
blinking at the top left corner, the computer not responding anymore.
I have to reboot by holding down the hardware button on the computer.
After the hard reboot, restart works as expected, until I reconfigure
the system again.

Powering off gives the same result, i.e. the computer freezes instead
of shutting down.  It doesn't matter whether I do it from inside Gnome
or a root console.

Does anyone else have this problem?  Could I manually restart some
service and then have restart work normally?

Thanks!

Re: blacklisting iwlwifi and reconfiguring guixsd from another distribution (manjaro)

[pelzflorian (Florian Pelz)]

Hello crodges.

On Sun, Apr 17, 2022 at 09:01:39PM -0700, crodges wrote:
> I mounted guixsd partition from manjaro and added the lines to blacklist 
> iwlwifi. But after that ... how can I reconfigure the system from manjaro, 
> reboot and use guix? I thought maybe I can try to use chroot somehow, but I'm 
> not sure how to proceed. If anyone knows a simpler way, please I wanna know.

The chroot procedure from Arch works fine
.

However, it may be simpler to just edit the boot options of your Guix
system (press e in GRUB) and add

modprobe.blacklist=pcspkr,snd_pcsp,iwlwifi

and reconfigure from there.

Regards,
Florian

blacklisting iwlwifi and reconfiguring guixsd from another distribution (manjaro)

[crodges]

Hello everyone,

With help from the community, I got guix installed in my main desktop in a 
partition. I also have another partition with manjaro and guix on top (manjaro 
is the foreign distribution). 

The problem with my bare metal guix installation is that it is hanging during 
boot when it tries to find free firmware for my wifi, and can't find. I don't 
need wifi because I got cabled internet. After speaking in the bug list and 
researching a little, I found this issue and I'm trying to add exactly the 
lines at https://issues.guix.gnu.org/53712#13 to blacklist iwlwifi, which 
seems to be a workaround.

I mounted guixsd partition from manjaro and added the lines to blacklist 
iwlwifi. But after that ... how can I reconfigure the system from manjaro, 
reboot and use guix? I thought maybe I can try to use chroot somehow, but I'm 
not sure how to proceed. If anyone knows a simpler way, please I wanna know.

crodges

signature.asc
Description: This is a digitally signed message part.

Reconfiguring syslogd flags

[Eric Brown]

Hello,

I am trying to set up a centralized syslogd server that listens on 514
(--inet flag):

 (syslog-service config =>
 (syslog-configuration
  (inherit config)
  (syslogd (string-append (assoc-ref inputs "inetutils") 
"/libexec/syslogd --inet"

and clients which should send a copy of all messages to that host:

 (syslog-service config =>
 (syslog-configuration
  (inherit config)
  (config-file
   (append '("*.* @10.0.0.2:514")
   %default-syslog.conf

However, ps aux | grep syslogd always shows the default values, as if
the above did not take.

(I can send/receive logs if I forcibly kill syslogd and run daemons on
command line with appropriate flag/files.)

Would anyone be able to tell me the right way to do this?

Thanks,
Eric

Re: reconfiguring

[Ricardo Wurmus]

myg...@gmail.com writes:

> On 02/13/2018 at 21:32 Andreas Enge writes:
>
>> On Tue, Feb 13, 2018 at 02:03:58PM -0500, Leo Famulari wrote:
>>> But, it doesn't try to stop and restart those services in case of any
>>> relevant changes, right? Doesn't that require a reboot?
>>
>> Yes, I understood so. I had the problem with my nginx server recently.
>> In that case, I needed to stop it before upgrading, and then it was
>> restarted automatically. However, when it was not stopped, it continued
>> running with the old configuration. It is not quite clear to me whether
>> this is a bug or a feature. I tend more towards bug... It is definitely
>> in contrast to what happens in Debian, for instance.
>
> This bug/feature bit me (also Debian user) recently ;-)
>
> Is this by design? Or a limitation if the current implementation?

It’s a bug; bug 22039 to be exact.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Re: reconfiguring

[myglc2]

On 02/13/2018 at 21:32 Andreas Enge writes:

> On Tue, Feb 13, 2018 at 02:03:58PM -0500, Leo Famulari wrote:
>> But, it doesn't try to stop and restart those services in case of any
>> relevant changes, right? Doesn't that require a reboot?
>
> Yes, I understood so. I had the problem with my nginx server recently.
> In that case, I needed to stop it before upgrading, and then it was
> restarted automatically. However, when it was not stopped, it continued
> running with the old configuration. It is not quite clear to me whether
> this is a bug or a feature. I tend more towards bug... It is definitely
> in contrast to what happens in Debian, for instance.

This bug/feature bit me (also Debian user) recently ;-)

Is this by design? Or a limitation if the current implementation?

Re: reconfiguring

[Ricardo Wurmus]

Carlo Zancanaro  writes:

> On Tue, Feb 13 2018, Ricardo Wurmus wrote:
>> That’s a misunderstanding.  All of the things in the “services”
>> field of
>> your operating-system configuration are “system services”, so
>> all of
>> them get updated.
>
> Should we think about changing the name for "system services"? The
> confusion with Shepherd services seems really easy to make. The
> Wikipedia article for GuixSD makes the same mistake, but I haven't
> had the chance to fix it yet. Maybe we should call them "system
> extensions", or "mixins", or something like that?

I would very much like to find a new term for them, because usually the
second thing I say about system services is that the naming is
unfortunate and collides with what people think is a shepherd service.

I’m not fond of “mixins” (this reminds me of the “traits”-like concept
in Ruby classes), nor do I really like “system extensions”, but I do
think that avoiding the naming conflict would be worth a bike-shed
discussion :)

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Re: reconfiguring

[Andreas Enge]

On Tue, Feb 13, 2018 at 02:03:58PM -0500, Leo Famulari wrote:
> But, it doesn't try to stop and restart those services in case of any
> relevant changes, right? Doesn't that require a reboot?

Yes, I understood so. I had the problem with my nginx server recently.
In that case, I needed to stop it before upgrading, and then it was
restarted automatically. However, when it was not stopped, it continued
running with the old configuration. It is not quite clear to me whether
this is a bug or a feature. I tend more towards bug... It is definitely
in contrast to what happens in Debian, for instance.

Andreas

Re: reconfiguring

[Leo Famulari]

On Wed, Feb 14, 2018 at 06:18:07AM +1100, Carlo Zancanaro wrote:
> 
> On Tue, Feb 13 2018, Leo Famulari wrote:
> > > That’s a misunderstanding.  All of the things in the “services”
> > > field of
> > > your operating-system configuration are “system services”, so all of
> > > them get updated.
> > 
> > But, it doesn't try to stop and restart those services in case of any
> > relevant changes, right? Doesn't that require a reboot?
> 
> The "system services" aren't services in the sense of being started/stopped.
> They are an extensible way to modify the system, such that one "service" can
> depend on another for its behaviour. For example, the `etc-service-type` is
> responsible for putting files in /etc, and so other services can "extend" it
> with files that they want placed in /etc. The concept of "starting" and
> "stopping" these services isn't really meaningful, because they just specify
> the state of the system. These services have an effect when you reconfigure.
> 
> One of the things that a "system service" can do is to register a Shepherd
> service. This is a process which will be invoked by Shepherd (pid 1), and
> can be started/stopped with the `herd` command. Reconfigure will not
> register any new Shepherd services, if doing so would involve starting an
> already-running service. So, for instance, you probably have a `guix-daemon`
> process running on your system. Reconfiguring your system will not upgrade
> (and thus restart) your `guix-daemon`. You need to reboot to have the new,
> updated, `guix-daemon` process. (Ideally you would only have to stop/start
> the Shepherd service manually to have the updated version, but at the moment
> doing so will just restart the old version.)
> 
> Hopefully that explanation is helpful. I also hope it's correct.

Thanks, that's a very helpful explanation!


signature.asc
Description: PGP signature

Re: reconfiguring

[Carlo Zancanaro]

On Tue, Feb 13 2018, Leo Famulari wrote:
That’s a misunderstanding.  All of the things in the “services” 
field of
your operating-system configuration are “system services”, so 
all of

them get updated.


But, it doesn't try to stop and restart those services in case 
of any

relevant changes, right? Doesn't that require a reboot?


The "system services" aren't services in the sense of being 
started/stopped. They are an extensible way to modify the system, 
such that one "service" can depend on another for its behaviour. 
For example, the `etc-service-type` is responsible for putting 
files in /etc, and so other services can "extend" it with files 
that they want placed in /etc. The concept of "starting" and 
"stopping" these services isn't really meaningful, because they 
just specify the state of the system. These services have an 
effect when you reconfigure.


One of the things that a "system service" can do is to register a 
Shepherd service. This is a process which will be invoked by 
Shepherd (pid 1), and can be started/stopped with the `herd` 
command. Reconfigure will not register any new Shepherd services, 
if doing so would involve starting an already-running service. So, 
for instance, you probably have a `guix-daemon` process running on 
your system. Reconfiguring your system will not upgrade (and thus 
restart) your `guix-daemon`. You need to reboot to have the new, 
updated, `guix-daemon` process. (Ideally you would only have to 
stop/start the Shepherd service manually to have the updated 
version, but at the moment doing so will just restart the old 
version.)


Hopefully that explanation is helpful. I also hope it's correct.

Carlo


signature.asc
Description: PGP signature

Re: reconfiguring

[Ricardo Wurmus]

Leo Famulari  writes:

> But, it doesn't try to stop and restart those services in case of any
> relevant changes, right? Doesn't that require a reboot?

Correct.  The manual says:

  "The command starts system services specified in file that are not
   currently running; if a service is currently running, it does not
   attempt to upgrade it since this would not be possible without
   stopping it first."

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Re: reconfiguring

[Carlo Zancanaro]

On Tue, Feb 13 2018, Ricardo Wurmus wrote:
That’s a misunderstanding.  All of the things in the “services” 
field of
your operating-system configuration are “system services”, so 
all of

them get updated.


Should we think about changing the name for "system services"? The 
confusion with Shepherd services seems really easy to make. The 
Wikipedia article for GuixSD makes the same mistake, but I haven't 
had the chance to fix it yet. Maybe we should call them "system 
extensions", or "mixins", or something like that?


Carlo


signature.asc
Description: PGP signature

Re: reconfiguring

[Leo Famulari]

On Tue, Feb 13, 2018 at 07:25:10PM +0100, Ricardo Wurmus wrote:
> 
> Catonano  writes:
> 
> > "The command starts system services specified in file that are not
> > currently running; if a service is currently running, it does not attempt
> > to upgrade it since this would not be possible without stopping it first."
> >
> > I was wondering: what about the desktop services ?
> >
> > I undertsand that my desktop session comes with a few services (in
> > %desktop-services or something)
> >
> > Does this mean that my desktop services do NOT get updated when I
> > reconfigure my system ?
> 
> That’s a misunderstanding.  All of the things in the “services” field of
> your operating-system configuration are “system services”, so all of
> them get updated.

But, it doesn't try to stop and restart those services in case of any
relevant changes, right? Doesn't that require a reboot?


signature.asc
Description: PGP signature

Re: reconfiguring

[Ricardo Wurmus]

Catonano  writes:

> "The command starts system services specified in file that are not
> currently running; if a service is currently running, it does not attempt
> to upgrade it since this would not be possible without stopping it first."
>
> I was wondering: what about the desktop services ?
>
> I undertsand that my desktop session comes with a few services (in
> %desktop-services or something)
>
> Does this mean that my desktop services do NOT get updated when I
> reconfigure my system ?

That’s a misunderstanding.  All of the things in the “services” field of
your operating-system configuration are “system services”, so all of
them get updated.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

reconfiguring

[Catonano]

About

guix system reconfigue some/conf-file.scm

I read in the manual that

"The command starts system services specified in file that are not
currently running; if a service is currently running, it does not attempt
to upgrade it since this would not be possible without stopping it first."

I was wondering: what about the desktop services ?

I undertsand that my desktop session comes with a few services (in
%desktop-services or something)

Does this mean that my desktop services do NOT get updated when I
reconfigure my system ?