[systemd-devel] hostnamectl doesn't work in a lxc container
Hi, Not sure it's a good place to ask. But it'd be great if you could help me with this one. Or at least tell me where to ask. I failed to find any systemd user mailing lists. The guys from lxc mailing list keep silence: https://lists.linuxcontainers.org/pipermail/lxc-users/2017-February/012840.html So, on one physical server in a lxc container I get this: # hostnamectl --static Could not get property: Connection timed out # hostnamectl # echo $? 1 Occasionally I get this error message: Could not get property: Failed to activate service 'org.freedesktop.hostname1': timed out And in the log I see this: Feb 10 12:39:04 server1 dbus[79]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Feb 10 12:39:05 server1 systemd[1]: Starting Hostname Service... Feb 10 12:39:05 server1 systemd[2935]: systemd-hostnamed.service: Failed at step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied Feb 10 12:39:05 server1 systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK Feb 10 12:39:05 server1 systemd[1]: Failed to start Hostname Service. Feb 10 12:39:05 server1 systemd[1]: systemd-hostnamed.service: Unit entered failed state. Feb 10 12:39:05 server1 systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'. Feb 10 12:39:29 server1 dbus[79]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out On the other server it works though. Here's what I see in the log: Feb 10 14:40:26 server2 dbus[25957]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Feb 10 14:40:26 server2 systemd[1]: Starting Hostname Service... Feb 10 14:40:26 server2 systemd-hostnamed[18340]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Feb 10 14:40:26 server2 dbus[25957]: [system] Successfully activated service 'org.freedesktop.hostname1' Feb 10 14:40:26 server2 systemd[1]: Started Hostname Service. What's causing it? What can I check? How do I remedy this? Thanks in advance. Regards, Yuri ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-bus-proxyd policy differences from dbus-daemon?
I'm trying to figure out the root cause of some failures of regular old libdbus1-using programs when /var/run/dbus/system_bus_socket happens to be provided by systemd-bus-proxyd. The programs in question attempt to invoke org.freedesktop.DBus.AddMatch() with the rule-parameter having the value: "type='signal',member='NameOwnerChanged',interface='org.freedesktop.DBus',path='/org/freedesktop/DBus',eavesdrop='false'". On a regular (non-kdbus) system, this doesn't cause dbus-daemon to raise its eyebrows, and the call succeeds. On a kdbus system, the bus proxy daemon reports back SD_BUS_ERROR_INVALID_ARGS (i.e., "org.freedesktop.DBus.Error.InvalidArgs" in the dbus wire protocol parlance). The source code to the bus proxy daemon seems to only reach this error condition when it judges the method request to have the wrong signature -- something other than a single in-parameter string. But that's not the case here as nearly as I can tell. Any chance that systemd-bus-proxyd has some nonobvious hard-wired allergy to the presence of the 'eavesdrop' attribute in that rule-string? -Matt ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Renew DHCP lease
I've just switched a server to systemd-networkd dhcp client. How do I renew a lease and/or force it to push a new hostname to the dhcp server. I have RTFM and get the impression it can't be done. Hopefully I have that wrong... Thanks and much appreciated. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] architecture: Add support for the RISC-V architecture.
On Fri, Feb 10, 2017 at 12:45:51PM +, Richard W.M. Jones wrote:
> On Fri, Sep 30, 2016 at 04:45:01PM +0100, Richard W.M. Jones wrote:
> > Signed-off-by: Richard W.M. Jones
> > ---
> > src/basic/architecture.c | 14 ++
> > src/basic/architecture.h | 16
> > 2 files changed, 30 insertions(+)
> >
> > diff --git a/src/basic/architecture.c b/src/basic/architecture.c
> > index b1c8e91..e1412be 100644
> > --- a/src/basic/architecture.c
> > +++ b/src/basic/architecture.c
> > @@ -123,6 +123,17 @@ int uname_architecture(void) {
> > { "crisv32",ARCHITECTURE_CRIS },
> > #elif defined(__nios2__)
> > { "nios2", ARCHITECTURE_NIOS2},
> > +#elif defined(__riscv__)
> > +{ "riscv32",ARCHITECTURE_RISCV32 },
> > +{ "riscv64",ARCHITECTURE_RISCV64 },
> > +{ "riscv128", ARCHITECTURE_RISCV128 },
> > +# if __SIZEOF_POINTER__ == 4
> > +{ "riscv", ARCHITECTURE_RISCV32 },
> > +# elif __SIZEOF_POINTER__ == 8
> > +{ "riscv", ARCHITECTURE_RISCV64 },
> > +# elif __SIZEOF_POINTER__ == 16
> > +{ "riscv", ARCHITECTURE_RISCV128 },
> > +# endif
>
> I just want to say that after this change, RISC-V unilaterally removed
> __riscv__ (and __riscv64 etc which other projects were using). I'm
> very annoyed about that as it breaks many patches that I sent upstream
> including to systemd.
>
> GCC changes for RISC-V have subsequently been accepted upstream, so
> they cannot do this again.
>
> The change is simply s/__riscv__/__riscv/g ie:
>
> > -#elif defined(__riscv__)
> > +#elif defined(__riscv)
>
> As we will need to rebuild the whole of Fedora/RISC-V to cope with
> this and other changes, I don't currently have a working GCC (and less
> still a working systemd) so I can't submit a formal patch right now.
>
> Rich.
https://github.com/systemd/systemd/pull/5304
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] architecture: Add support for the RISC-V architecture.
On Fri, Sep 30, 2016 at 04:45:01PM +0100, Richard W.M. Jones wrote:
> Signed-off-by: Richard W.M. Jones
> ---
> src/basic/architecture.c | 14 ++
> src/basic/architecture.h | 16
> 2 files changed, 30 insertions(+)
>
> diff --git a/src/basic/architecture.c b/src/basic/architecture.c
> index b1c8e91..e1412be 100644
> --- a/src/basic/architecture.c
> +++ b/src/basic/architecture.c
> @@ -123,6 +123,17 @@ int uname_architecture(void) {
> { "crisv32",ARCHITECTURE_CRIS },
> #elif defined(__nios2__)
> { "nios2", ARCHITECTURE_NIOS2},
> +#elif defined(__riscv__)
> +{ "riscv32",ARCHITECTURE_RISCV32 },
> +{ "riscv64",ARCHITECTURE_RISCV64 },
> +{ "riscv128", ARCHITECTURE_RISCV128 },
> +# if __SIZEOF_POINTER__ == 4
> +{ "riscv", ARCHITECTURE_RISCV32 },
> +# elif __SIZEOF_POINTER__ == 8
> +{ "riscv", ARCHITECTURE_RISCV64 },
> +# elif __SIZEOF_POINTER__ == 16
> +{ "riscv", ARCHITECTURE_RISCV128 },
> +# endif
I just want to say that after this change, RISC-V unilaterally removed
__riscv__ (and __riscv64 etc which other projects were using). I'm
very annoyed about that as it breaks many patches that I sent upstream
including to systemd.
GCC changes for RISC-V have subsequently been accepted upstream, so
they cannot do this again.
The change is simply s/__riscv__/__riscv/g ie:
> -#elif defined(__riscv__)
> +#elif defined(__riscv)
As we will need to rebuild the whole of Fedora/RISC-V to cope with
this and other changes, I don't currently have a working GCC (and less
still a working systemd) so I can't submit a formal patch right now.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
