Re: Improper shutdown, now Kernel panic.

2019-09-14 Thread murph nj
On Tue, Sep 10, 2019 at 2:52 PM Roger Heflin  wrote:
>
> Symbolic links missing on / (/bin->/usr/bin and such).
> /bin/bash missing or corrupted.
> /lib64/ libraries missing or corrupted.
> systemd itself missing, pivot root attempts to run systemd and that
> may be what is failing, but you don't really know what the underlying
> cause is for it to fail.
>
> What exactly was the "improper shutdown"
>
> The easiest way to debug is to livecd boot it mount up the old
> filessystems on say /oldroot (rootfs) mount /oldroot/usr for usr and
> so forth and then cd /oldroot and do a "chroot ."
>
> I would expect the chroot . to fail with some sort of error that may
> hint at what is broken.
>
> On Tue, Sep 10, 2019 at 7:15 AM murph nj  wrote:
> >
> > On Mon, Sep 9, 2019 at 9:07 PM Tony Nelson  
> > wrote:
> > >
> > > Usually, when it all goes wrong just after pivot-root, there is a
> > > problem with the new (real) root.  Exactly how it goes wrong is not
> > > useful.  I would look hard at whatever is mounted at /sysroot.  It
> > > should be what you expect / (root) to be, but mounted ro at that point
> > > (`cat /proc/mounts` should show it mounted at /sysroot (see `man 5
> > > fstab`
> > > for format); `ls -l /sysroot` should show the contents you expect).
> > > (All off the top of my head; I haven't rebooted to test.)

I was able to mount all of the boot drives, and it seemed OK, I
couldn't see anything that was out of order.

Unfortunately, I'm going to need this laptop next weekend, so my
journey of discovery on this is going to have to end, since I couldn't
fix it, I'll have to reload.  We gave it a shot though, and I have
some new things to try for other potential issues.

Again thanks for the help.

  --murph
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: ssh

2019-09-14 Thread Ed Greshko
On 9/15/19 1:19 AM, Patrick Dupre wrote:
> Here is the bizarre thing:
> from a gnome-shell
> telnet 192.168.1.12 22
> Trying 192.168.1.12...
> Connected to 192.168.1.12.
> Escape character is '^]'.
> SSH-2.0-OpenSSH_8.0
>
> Invalid SSH identification string.
> Connection closed by foreign host.

That's good.  Shows port 22 is open.

>
> ssh 192.168.1.12 22
> time out
>
> But
> from a terminal (ttx)
> the ssh works perfectly well!
>
> What is wrong with the gnome environment?

First, the format of the command is wrong.  The "22" is a command to be 
executed on the remote side.
Do "man ssh" and "man telnet" to learn about the format of the command.

Now, as for what is wrong with the "gnome environment"/

What is the output of "which ssh"?  It should be

[egreshko@meimei ~]$ which ssh
/usr/bin/ssh



-- 
If simple questions can be answered with a simple google query then why are 
there so many of them?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: ssh

2019-09-14 Thread Patrick Dupre
Here is the bizarre thing:
from a gnome-shell
telnet 192.168.1.12 22
Trying 192.168.1.12...
Connected to 192.168.1.12.
Escape character is '^]'.
SSH-2.0-OpenSSH_8.0

Invalid SSH identification string.
Connection closed by foreign host.

ssh 192.168.1.12 22
time out

But
from a terminal (ttx)
the ssh works perfectly well!

What is wrong with the gnome environment?


>
>
> > Date: Saturday, September 14, 2019 22:13:11 +0800
> > From: Ed Greshko 
>
> >>> On 9/14/19 9:34 PM, Patrick Dupre wrote:
>
> >
> >>> From the remote system, what do you get when you try to "telnet"
> >>> to port 22?
> >>>
> >> telnet 192.168.1.12
> >> Trying 192.168.1.12...
> >> telnet: connect to address 192.168.1.12: No route to host
> >>
> >> I guess that I need to reestablish the route.
> >> How?
> >>
> >
> > No, that is an indication that port 22 is not open.
> >
>
> Actually, it looks like you did a telnet to the (default) telnet port
> (23):
>
>   > telnet 192.168.1.12
>
> rather than the ssh port (22), as Ed suggested:
>
>   > telnet 192.168.1.12 22
>
> which is what is needed to get meaningful results.
>
> Try the telnet to the ssh port and see what you get. It may be a
> firewall issue, but the results you showed don't appear to be a test
> of the issue.
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: ssh

2019-09-14 Thread Ed Greshko
On 9/14/19 11:41 PM, Richard wrote:
> Actually, it looks like you did a telnet to the (default) telnet port
> (23):
>
>   > telnet 192.168.1.12
>
> rather than the ssh port (22), as Ed suggested:

Thanks!  Good Catch.

I only looked at the end result.  Gotta get out of the habit of expecting 
someone to do as requested.  :-) :-)

-- 
If simple questions can be answered with a simple google query then why are 
there so many of them?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: ssh

2019-09-14 Thread Richard

> Date: Saturday, September 14, 2019 22:13:11 +0800
> From: Ed Greshko 

>>> On 9/14/19 9:34 PM, Patrick Dupre wrote:

> 
>>> From the remote system, what do you get when you try to "telnet"
>>> to port 22?
>>> 
>> telnet 192.168.1.12
>> Trying 192.168.1.12...
>> telnet: connect to address 192.168.1.12: No route to host
>> 
>> I guess that I need to reestablish the route.
>> How?
>> 
> 
> No, that is an indication that port 22 is not open.
> 

Actually, it looks like you did a telnet to the (default) telnet port
(23):

  > telnet 192.168.1.12

rather than the ssh port (22), as Ed suggested:

  > telnet 192.168.1.12 22

which is what is needed to get meaningful results. 

Try the telnet to the ssh port and see what you get. It may be a
firewall issue, but the results you showed don't appear to be a test
of the issue.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: ssh

2019-09-14 Thread Ed Greshko
On 9/14/19 10:13 PM, Ed Greshko wrote:
> On 9/14/19 9:59 PM, Patrick Dupre wrote:
>>> On 9/14/19 9:34 PM, Patrick Dupre wrote:
 Hello,

 ssh does not respond (time out, the machine is OK). Hence, I restarted it 
 and

 systemctl status sshd
 ● sshd.service - OpenSSH server daemon
Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor 
 preset>
Active: active (running) since Sat 2019-09-14 15:26:06 CEST; 32s ago
  Docs: man:sshd(8)
man:sshd_config(5)
  Main PID: 29012 (sshd)
 Tasks: 1 (limit: 4915)
Memory: 1.0M
CGroup: /system.slice/sshd.service
└─29012 /usr/sbin/sshd -D 
 -oCiphers=aes256-...@openssh.com,chacha20->

 Sep 14 15:26:06 Teucidide systemd[1]: Starting OpenSSH server daemon...
 Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on 0.0.0.0 port 22.
 Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on :: port 22.
 Sep 14 15:26:06 Teucidide systemd[1]: Started OpenSSH server daemon.


 But it is not enough.
 What else should I do?
>>> I assume you mean that when you attempt to ssh to the machine from a remote 
>>> system it times out?
>>>
>>> First Q is, did you make sure port 22 is opened on the server?
>> I guess, from the machine itself (192.168.1.12), the ssh works OK
> That doesn't tell you anything.  The firewall doesn't block connections on 
> the server to the server.
>
>>> From the remote system, what do you get when you try to "telnet" to port 22?
>>>
>> telnet 192.168.1.12
>> Trying 192.168.1.12...
>> telnet: connect to address 192.168.1.12: No route to host
>>
>> I guess that I need to reestablish the route.
>> How?
>>
> No, that is an indication that port 22 is not open.
>
> On the server you should see ssh included like so in this command
>
> [root@f31bk ~]# firewall-cmd --permanent --list-services
> dhcpv6-client mdns ssh
>
> If not listed, you can then do
>
> firewall-cmd --permanent --add-service=ssh
>

Oh, you may also have to do "firewall-cmd --add-service=ssh"

for immediate effect.

-- 
If simple questions can be answered with a simple google query then why are 
there so many of them?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: ssh

2019-09-14 Thread Ed Greshko
On 9/14/19 9:59 PM, Patrick Dupre wrote:
>> On 9/14/19 9:34 PM, Patrick Dupre wrote:
>>> Hello,
>>>
>>> ssh does not respond (time out, the machine is OK). Hence, I restarted it 
>>> and
>>>
>>> systemctl status sshd
>>> ● sshd.service - OpenSSH server daemon
>>>Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor 
>>> preset>
>>>Active: active (running) since Sat 2019-09-14 15:26:06 CEST; 32s ago
>>>  Docs: man:sshd(8)
>>>man:sshd_config(5)
>>>  Main PID: 29012 (sshd)
>>> Tasks: 1 (limit: 4915)
>>>Memory: 1.0M
>>>CGroup: /system.slice/sshd.service
>>>└─29012 /usr/sbin/sshd -D 
>>> -oCiphers=aes256-...@openssh.com,chacha20->
>>>
>>> Sep 14 15:26:06 Teucidide systemd[1]: Starting OpenSSH server daemon...
>>> Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on 0.0.0.0 port 22.
>>> Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on :: port 22.
>>> Sep 14 15:26:06 Teucidide systemd[1]: Started OpenSSH server daemon.
>>>
>>>
>>> But it is not enough.
>>> What else should I do?
>> I assume you mean that when you attempt to ssh to the machine from a remote 
>> system it times out?
>>
>> First Q is, did you make sure port 22 is opened on the server?
> I guess, from the machine itself (192.168.1.12), the ssh works OK

That doesn't tell you anything.  The firewall doesn't block connections on the 
server to the server.

>> From the remote system, what do you get when you try to "telnet" to port 22?
>>
> telnet 192.168.1.12
> Trying 192.168.1.12...
> telnet: connect to address 192.168.1.12: No route to host
>
> I guess that I need to reestablish the route.
> How?
>

No, that is an indication that port 22 is not open.

On the server you should see ssh included like so in this command

[root@f31bk ~]# firewall-cmd --permanent --list-services
dhcpv6-client mdns ssh

If not listed, you can then do

firewall-cmd --permanent --add-service=ssh




-- 
If simple questions can be answered with a simple google query then why are 
there so many of them?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: ssh

2019-09-14 Thread Patrick Dupre
> On 9/14/19 9:34 PM, Patrick Dupre wrote:
> > Hello,
> >
> > ssh does not respond (time out, the machine is OK). Hence, I restarted it 
> > and
> >
> > systemctl status sshd
> > ● sshd.service - OpenSSH server daemon
> >Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor 
> > preset>
> >Active: active (running) since Sat 2019-09-14 15:26:06 CEST; 32s ago
> >  Docs: man:sshd(8)
> >man:sshd_config(5)
> >  Main PID: 29012 (sshd)
> > Tasks: 1 (limit: 4915)
> >Memory: 1.0M
> >CGroup: /system.slice/sshd.service
> >└─29012 /usr/sbin/sshd -D 
> > -oCiphers=aes256-...@openssh.com,chacha20->
> >
> > Sep 14 15:26:06 Teucidide systemd[1]: Starting OpenSSH server daemon...
> > Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on 0.0.0.0 port 22.
> > Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on :: port 22.
> > Sep 14 15:26:06 Teucidide systemd[1]: Started OpenSSH server daemon.
> >
> >
> > But it is not enough.
> > What else should I do?
> 
> I assume you mean that when you attempt to ssh to the machine from a remote 
> system it times out?
> 
> First Q is, did you make sure port 22 is opened on the server?
I guess, from the machine itself (192.168.1.12), the ssh works OK
> 
> From the remote system, what do you get when you try to "telnet" to port 22?
> 
telnet 192.168.1.12
Trying 192.168.1.12...
telnet: connect to address 192.168.1.12: No route to host

I guess that I need to reestablish the route.
How?


> It should be simiiar to this
> 
> [egreshko@meimei ~]$ telnet 192.168.1.55 22
> Trying 192.168.1.55...
> Connected to 192.168.1.55.
> Escape character is '^]'.
> SSH-2.0-OpenSSH_8.0
> ^]
> telnet> close
> Connection closed.
> 
> 
> 
> 
> -- 
> If simple questions can be answered with a simple google query then why are 
> there so many of them?
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


Re: ssh

2019-09-14 Thread Ed Greshko
On 9/14/19 9:34 PM, Patrick Dupre wrote:
> Hello,
>
> ssh does not respond (time out, the machine is OK). Hence, I restarted it and
>
> systemctl status sshd
> ● sshd.service - OpenSSH server daemon
>Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor 
> preset>
>Active: active (running) since Sat 2019-09-14 15:26:06 CEST; 32s ago
>  Docs: man:sshd(8)
>man:sshd_config(5)
>  Main PID: 29012 (sshd)
> Tasks: 1 (limit: 4915)
>Memory: 1.0M
>CGroup: /system.slice/sshd.service
>└─29012 /usr/sbin/sshd -D 
> -oCiphers=aes256-...@openssh.com,chacha20->
>
> Sep 14 15:26:06 Teucidide systemd[1]: Starting OpenSSH server daemon...
> Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on 0.0.0.0 port 22.
> Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on :: port 22.
> Sep 14 15:26:06 Teucidide systemd[1]: Started OpenSSH server daemon.
>
>
> But it is not enough.
> What else should I do?

I assume you mean that when you attempt to ssh to the machine from a remote 
system it times out?

First Q is, did you make sure port 22 is opened on the server?

From the remote system, what do you get when you try to "telnet" to port 22?

It should be simiiar to this

[egreshko@meimei ~]$ telnet 192.168.1.55 22
Trying 192.168.1.55...
Connected to 192.168.1.55.
Escape character is '^]'.
SSH-2.0-OpenSSH_8.0
^]
telnet> close
Connection closed.




-- 
If simple questions can be answered with a simple google query then why are 
there so many of them?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


ssh

2019-09-14 Thread Patrick Dupre
Hello,

ssh does not respond (time out, the machine is OK). Hence, I restarted it and

systemctl status sshd
● sshd.service - OpenSSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset>
   Active: active (running) since Sat 2019-09-14 15:26:06 CEST; 32s ago
 Docs: man:sshd(8)
   man:sshd_config(5)
 Main PID: 29012 (sshd)
Tasks: 1 (limit: 4915)
   Memory: 1.0M
   CGroup: /system.slice/sshd.service
   └─29012 /usr/sbin/sshd -D -oCiphers=aes256-...@openssh.com,chacha20->

Sep 14 15:26:06 Teucidide systemd[1]: Starting OpenSSH server daemon...
Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on 0.0.0.0 port 22.
Sep 14 15:26:06 Teucidide sshd[29012]: Server listening on :: port 22.
Sep 14 15:26:06 Teucidide systemd[1]: Started OpenSSH server daemon.


But it is not enough.
What else should I do?

Thank.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
 Tel: +33 (0)380395988
===
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


kernel error: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request.

2019-09-14 Thread Cătălin George Feștilă
I got this error on cockpit and I want to fix it:
13:13 [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for 
forcewake ack request. kernel
The content of this error is:
[drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack 
request.
PRIORITY3
SYSLOG_FACILITY 0
SYSLOG_IDENTIFIER   kernel
_BOOT_ID9776d68cb00f4af8b0802e8854622895
_HOSTNAME   desk
_MACHINE_ID 743fe09e4d084e9482e810d5e8383991
_SOURCE_MONOTONIC_TIMESTAMP 4100878
_TRANSPORT  kernel
__CURSOR
s=0690b0952f46407496430419209c9ebb;i=2a1;b=9776d68cb00f4af8b0802e8854622895;m=3e7a55;t=59280a107bb8d;x=5217a82e936b0a19
__MONOTONIC_TIMESTAMP   4094549
__REALTIME_TIMESTAMP1568456038661005
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org