Displaying 20 results from an estimated 10000 matches similar to: "systemctl reboot -- server not accessible after reboot"
2017 Oct 15
2
systemctl reboot -- server not accessible after reboot
On Sat, Oct 14, 2017 at 6:24 PM, Jonathan Billings <billings at negate.org> wrote:
>
> When you say that the monitor is plugged in, and the server is unresponsive, does that mean that the monitor doesn?t even come active? That sounds like it might have crashed the kernel in a way that the display isn?t showing.
>
> You could set up kdump to catch that. You could also set up a
2017 Oct 14
0
systemctl reboot -- server not accessible after reboot
On Oct 14, 2017, at 1:54 PM, Mike <1100100 at gmail.com> wrote:
> Server disconnects my ssh connection and never comes back up.
> Go to the server and the power is on but the server is not accessible by ssh.
> When I connect a monitor and keyboard --- non-responsive. It's like
> it's in suspend mode.
>
> I push and hold the power button until the server fully
2017 Oct 15
1
systemctl reboot -- server not accessible after reboot
On Sat, Oct 14, 2017 at 2:29 PM, Vitalino Victor <vitalinobr at gmail.com> wrote:
>
> Try:
>
> # shutdown -r now
>
I'll have to try this late one evening.
It's a production Samba Active Directory Domain Controller in
production so it's difficult to do this without warning to users.
2017 Oct 14
0
systemctl reboot -- server not accessible after reboot
Am 14.10.2017 um 19:54 schrieb Mike:
> Hi,
>
> Such a simple problem, but I can't figure out the cause.
> Supermicro server with a Xeon E3-1200 cpu.
> 1U entry level item.
>
> Using CentOS 7
The version is a bit unprecise. Are you fully updated?
On 7.3 and 7.4 I haven't seen that issue.
> from ~$root --- systemctl reboot
>
> Server disconnects my ssh
2017 Oct 14
0
systemctl reboot -- server not accessible after reboot
Hi,
I have this problem!
Try:
# shutdown -r now
For a test, please...
2017-10-14 14:54 GMT-03:00 Mike <1100100 at gmail.com>:
> Hi,
>
> Such a simple problem, but I can't figure out the cause.
> Supermicro server with a Xeon E3-1200 cpu.
> 1U entry level item.
>
> Using CentOS 7
>
> from ~$root --- systemctl reboot
>
> Server disconnects my ssh
2015 Apr 04
4
systemctl (again)
On April 4, 2015 12:14:08 PM EDT, Pete Travis <lists at petetravis.com> wrote:
>On Apr 4, 2015 7:55 AM, "J Martin Rushton"
><martinrushton56 at btinternet.com>
>wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Thanks Andrew.
>>
>> One more problem solved, as I discovered last thing yesterday there
>>
2012 Jul 05
10
[PATCH] kexec-tools: Read always one vmcoreinfo file
vmcoreinfo file could exists under /sys/kernel (valid on baremetal only)
and/or under /sys/hypervisor (valid when Xen dom0 is running).
Read only one of them. It means that only one PT_NOTE will be
always created. Remove extra code for second PT_NOTE creation.
Signed-off-by: Daniel Kiper <daniel.kiper@oracle.com>
---
kexec/crashdump-elf.c | 33 +++++++--------------------------
1 files
2017 Oct 15
0
systemctl reboot -- server not accessible after reboot
Thank you for your thoughtful responses.
Very much appreciated.
Good points to follow up with.
Kind regards,
Mike
2015 Apr 04
2
systemctl (again)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thanks Andrew.
One more problem solved, as I discovered last thing yesterday there
was a missing "[Install]". Using your copy of the httpd service I
cut-and-pasted it onto the end of the service file you'd given me
earlier and at last was able to load the service. It wouldn't run,
but at least it was some progress.
I ran
2019 Dec 02
1
several VMs have suddenly quit working, in VBox.
Hi all!
I have several VMs, all in virtualbox 6.0.14 and all the VBOX add-ons are
up to date.
I don't use them daily, last used any of them probably 4-6 weeks ago,
pretty sure it was already running 6.0.14 by that time. they were all
fine when last used.
Two of them are C7, one is a clone of the other, and the other is C8.
each seems to have different symptoms.
the C7 clone claims there
2007 Sep 28
18
[makedumpfile] extract vmcoreinfo from /proc/vmcore for Xen
Hi,
--- background ----------------------------------------------------
* what the makedumpfile is:
To shorten the size of the dumpfile and the time of creating the
dumpfile, makedumpfile copies only the necessary pages for analysis
to the dumpfile from /proc/vmcore. You can specify the kind of
unnecessary pages with dump_level. If you want to shorten the size
further, enable the
2019 Dec 13
5
systemctl behaves like it is being piped to less in centos 8?
Comparing the output of systemctl between centos 7 and 8:
[root at mail ~]# cat /etc/redhat-release
CentOS Linux release 7.7.1908 (Core)
[root at mail ~]# systemctl status firewalld
? firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled;
vendor preset: enabled)
Active: active (running) since Fri 2019-10-25 00:24:24 UTC; 1
2017 Dec 15
2
ot: 2.2 ghettoforge install systemctl Q
I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used
/etc/dovecot from current Centos 6 Dovecot 2.1
I can start/stop Dovecot with dovecot / doveadm stop
BUT when I tried 'systemctl' I get
# systemctl status dovecot
? dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled;
vendor preset: disabled)
2017 Dec 16
1
ot: 2.2 ghettoforge install systemctl Q
On 16/12/17 20:45, Aki Tuomi wrote:
>> I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used
>> /etc/dovecot from current Centos 6 Dovecot 2.1
>>
>> I can start/stop Dovecot with dovecot / doveadm stop
>>
>> BUT when I tried 'systemctl' I get
>>
>> # systemctl status dovecot
>> ? dovecot.service - Dovecot IMAP/POP3
2016 Apr 28
1
systemctl enable httpd failure
Hi List,
[root at mail1 ~]# systemctl enable httpd
Failed to execute operation: Invalid argument
I can disable and re-enable other services without issue, I'm also
seeing the same error when I run
[root at mail1 ~]# systemctl enable mailman
Failed to execute operation: Invalid argument
Any suggestions?
Michael
2014 Sep 01
2
Runing multiple daemons with systemctl
Hi all,
I am doing some tests with a CentOS7 vm image before to enter in our
production environment. I need to migrate some sysvinit scripts to
systemctl.
In all of them I need to launch some daemons in the same init script.
For example:
a) start daemon1
b) if daemon1 returns no startup errors, launch daemon2
c) if daemon1 returns any startup error, doesn't start daemon2 and exit.
Is it
2015 Apr 03
2
systemctl (again)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yet more information:
As a test I moved the link
/etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service into
/etc/systemd/user and reran systemctl daemon-reload. I then rebooted.
# ls -l /etc/systemd/user
total 4
lrwxrwxrwx. 1 root root 41 Jul 27 2014
dbus-org.fedoraproject.FirewallD1.service ->
2015 Apr 02
4
systemctl (again)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
SELinux certainly was causing fun and games. I copied your suggestion
to /etc/systemd/user/timidity.service (mode 750) but it's still not happy:
[root at tamar user]# systemctl status timidity
timidity.service
Loaded: not-found (Reason: No such file or directory)
Active: failed (Result: exit-code) since Th...
... Starting LSB: Add
2019 Feb 25
2
Restarting nfs-server using systemctl resulted in error
Hi All,
I am having strange issues with NFS server on CentOS 7.2. I am unable to
restart the nfs-server:
[root at hostname ~]# systemctl restart nfs-server
** (pkttyagent:20603): WARNING **: Unable to register authentication agent:
Timeout was reached
Error registering authentication agent: Timeout was reached
(g-io-error-quark, 24)
Failed to restart nfs-server.service: Connection timed out
2020 Apr 30
2
systemctl restart changes permission.
Hi,
I am running CentOS Linux release 7.8.2003 (Core)
with php72u-fpm-7.2.30-1.el7.ius.x86_64 version. I am facing the below
permission denied issue. I also did the below steps
#cd /run
#chown -Rc nginx.nginx php-fpm
changed ownership of ?php-fpm/php-fpm.pid? from root:root to nginx:nginx
changed ownership of ?php-fpm? from root:root to nginx:nginx
#systemctl restart php-fpm again changes it from