Re:Re: [gentoo-user] systemd-journald: user-1000.journal ... Not a XENIX named type file
No. I suspect that the battery on the mainboard is too old to keep the clock working on the mainboard. But the time of the boot shown on the screen is later than the last boot, and the time after my login is a little later than the previous journal file. Does it matter to keep the clock exact? I always think that the boot time later than the previous shutdown time is just OK. At 2023-02-26 10:57:37, "Matt Connell" wrote: >On Sun, 2023-02-26 at 10:31 +0800, johnstrass wrote: >> Monotonic clock jumped backwards relative last journal entry > >Is your system clock accurate? Is it in sync the the hardware clock, >if the machine has one? >
Re: [gentoo-user] systemd-journald: user-1000.journal ... Not a XENIX named type file
On Sun, 2023-02-26 at 10:31 +0800, johnstrass wrote: > Monotonic clock jumped backwards relative last journal entry Is your system clock accurate? Is it in sync the the hardware clock, if the machine has one?
[gentoo-user] systemd-journald: user-1000.journal ... Not a XENIX named type file
Hi there, I am using a Loongson2f Yeeloong netbook and have upgraded to kernel 6.0.5. When I boot and login after typing the password, systemd-journald shows: systemd-journald [144]:/var/log/journal/67er8fc429e5364af4fe1074626r7e38/user-1000.journal: Monotonic clock jumped backwards relative last journal entry, rotating. systemd-journald[144]: Failed to write entry to /var/log/jourmal/67er8fc429e5364af4fe1074626r7e38/user-1000.journal (30 items, 791 bytes ), rotating before retrying : not a XENIX named type file Is this a serious problem? What can I do to avoid this? Thanks.
Re: [gentoo-user] [SOLVED] Nextcloud-24.0.7 and proxy settings
Hi there, The problem has a rather simple cause and also a simple solution: Nextcloud expects a working DNS server for resolving its own app server, *then* it is using the proxy to access it. After configuring a DNS proxy in my DMZ and ensuring that /etc/resolv.conf on the nextcloud instance is correctly pointing to it, it suddenly works :-) Alex On Sonntag, 19. Februar 2023, 13:17:41 CET Alexander Puchmayr wrote: > Hi there, > > I'm trying to setup a nextcloud instance inside a DMZ that has no direct > connection to the outside world, only via proxy. The proxy itself is working > fine, but I fail to configure nextcloud to actually use this proxy. > > According to the docs, I tried setting the proxy field in config/config.php, > i.e. > > $CONFIG = array ( > ... > 'proxy' => '10.46.1.109:3128', > 'proxyuserpwd' => '', > ... > ); > > But this setting seems to be ignored, tcpdump does not show any connection > attempt to that ip and nextcloud complains that it cannot connect to the > internet. > > In another forum I found that in > /etc/apache2/vhosts.d/10_nextcloud_vhosts.conf, environment variables like > HTTP_PROXY and HTTPS_PROXY may be set, i.e. > > > ... > SetEnv HTTP_PROXY 10.46.1.109:3128 > SetEnv HTTPS_PROXY 10.46.1.109:3128 > ... > > > But this also does not seem to work. > > Any other ideas? > > Thanks > Alex
