Today at 13:00 my other computer suddenly became dark in KDE under Leap 15.4, recently installed. Then I opened a console and found out that tcsh does not work any more. I prepared three very simple scripts for testing purposes: -rwxr-xr-x 1 wolfgang 28 Jun 14 15:41 script.tcsh -rwxr-xr-x 1 wolfgang 27 Jun 14 15:57 script.sh -rwxr-xr-x 1 wolfgang 29 Jun 14 15:45 script.bash script.tcsh, consists of these 2 lines: #!/bin/csh echo 'Hi, world' script.sh, consists of these 2 lines: #!/bin/sh echo 'Hi, world and script.bash, consists of these 2 lines: #!/bin/bash echo 'Hi, world' Invoking them directly fails, yielding the error messages: script.tcsh: Command not found. script.sh: Command not found. script.bash: Command not found. When I invoke one of them specifying "tcsh", i.e. tcsh-prompt> tcsh script.tcsh the script hangs and has to be dropped with CTRL C. The same for tcsh-prompt> sh script.sh and tcsh-prompt> bash script.bash. The only way to make the scripts work is invoking them in a bash session. Now bash-prompt> tcsh script.tcsh hangs again, but bash-prompt> sh script.sh and bash-prompt> bash script.bash work correctly, producing the output Hi, world But even in a bash session, it is not possible to invoke the scripts directly. Anyway, I urgently need tcsh, having a lot of scripts working under tcsh or csh only. Thanks in advance for your help, Wolfgang
On 14.06.2022 17:57, Wolfgang Mueller wrote:
Today at 13:00 my other computer suddenly became dark in KDE under Leap 15.4, recently installed. Then I opened a console and found out that tcsh does not work any more. I prepared three very simple scripts for testing purposes:
-rwxr-xr-x 1 wolfgang 28 Jun 14 15:41 script.tcsh -rwxr-xr-x 1 wolfgang 27 Jun 14 15:57 script.sh -rwxr-xr-x 1 wolfgang 29 Jun 14 15:45 script.bash
script.tcsh, consists of these 2 lines: #!/bin/csh echo 'Hi, world'
script.sh, consists of these 2 lines: #!/bin/sh echo 'Hi, world
and script.bash, consists of these 2 lines: #!/bin/bash echo 'Hi, world'
Invoking them directly fails, yielding the error messages: script.tcsh: Command not found. script.sh: Command not found. script.bash: Command not found.
Which is expected as current working directory is not in PATH by default.
When I invoke one of them specifying "tcsh", i.e. tcsh-prompt> tcsh script.tcsh the script hangs and has to be dropped with CTRL C. The same for tcsh-prompt> sh script.sh and tcsh-prompt> bash script.bash.
The only way to make the scripts work is invoking them in a bash session. Now bash-prompt> tcsh script.tcsh hangs again, but bash-prompt> sh script.sh and bash-prompt> bash script.bash work correctly, producing the output Hi, world
But even in a bash session, it is not possible to invoke the scripts directly.
Anyway, I urgently need tcsh, having a lot of scripts working under tcsh or csh only.
Could be something wrong with filesystem or hard disk. Upload full output of "journalctl -b" to https://susepaste.org/
On Tue, 14 Jun 2022 at 17:59:24 +0200, Andrei Borzenkov wrote:
On 14.06.2022 17:57, Wolfgang Mueller wrote:
Today at 13:00 my other computer suddenly became dark in KDE under Leap 15.4, recently installed. Then I opened a console and found out that tcsh does not work any more. I prepared three very simple scripts for testing purposes:
-rwxr-xr-x 1 wolfgang 28 Jun 14 15:41 script.tcsh -rwxr-xr-x 1 wolfgang 27 Jun 14 15:57 script.sh -rwxr-xr-x 1 wolfgang 29 Jun 14 15:45 script.bash
script.tcsh, consists of these 2 lines: #!/bin/csh echo 'Hi, world'
script.sh, consists of these 2 lines: #!/bin/sh echo 'Hi, world
and script.bash, consists of these 2 lines: #!/bin/bash echo 'Hi, world'
Invoking them directly fails, yielding the error messages: script.tcsh: Command not found. script.sh: Command not found. script.bash: Command not found.
Which is expected as current working directory is not in PATH by default.
When I invoke one of them specifying "tcsh", i.e. tcsh-prompt> tcsh script.tcsh the script hangs and has to be dropped with CTRL C. The same for tcsh-prompt> sh script.sh and tcsh-prompt> bash script.bash.
The only way to make the scripts work is invoking them in a bash session. Now bash-prompt> tcsh script.tcsh hangs again, but bash-prompt> sh script.sh and bash-prompt> bash script.bash work correctly, producing the output Hi, world
But even in a bash session, it is not possible to invoke the scripts directly.
Anyway, I urgently need tcsh, having a lot of scripts working under tcsh or csh only.
Could be something wrong with filesystem or hard disk. Upload full output of "journalctl -b" to https://susepaste.org/
Not knowing how to get access to the site indicated by you, I wrote the output of "journalctl -b" on my own site: http://www.ariannuccia.de/temp/Borzenkov/journalctl-b.html Best regards and thank you for your help, Wolfgang
On 14.06.2022 19:48, Wolfgang Mueller wrote:
On Tue, 14 Jun 2022 at 17:59:24 +0200, Andrei Borzenkov wrote:
On 14.06.2022 17:57, Wolfgang Mueller wrote:
Today at 13:00 my other computer suddenly became dark in KDE under Leap 15.4, recently installed. Then I opened a console and found out that tcsh does not work any more. I prepared three very simple scripts for testing purposes:
-rwxr-xr-x 1 wolfgang 28 Jun 14 15:41 script.tcsh -rwxr-xr-x 1 wolfgang 27 Jun 14 15:57 script.sh -rwxr-xr-x 1 wolfgang 29 Jun 14 15:45 script.bash
script.tcsh, consists of these 2 lines: #!/bin/csh echo 'Hi, world'
script.sh, consists of these 2 lines: #!/bin/sh echo 'Hi, world
and script.bash, consists of these 2 lines: #!/bin/bash echo 'Hi, world'
Invoking them directly fails, yielding the error messages: script.tcsh: Command not found. script.sh: Command not found. script.bash: Command not found.
Which is expected as current working directory is not in PATH by default.
When I invoke one of them specifying "tcsh", i.e. tcsh-prompt> tcsh script.tcsh the script hangs and has to be dropped with CTRL C. The same for tcsh-prompt> sh script.sh and tcsh-prompt> bash script.bash.
The only way to make the scripts work is invoking them in a bash session. Now bash-prompt> tcsh script.tcsh hangs again, but bash-prompt> sh script.sh and bash-prompt> bash script.bash work correctly, producing the output Hi, world
But even in a bash session, it is not possible to invoke the scripts directly.
Anyway, I urgently need tcsh, having a lot of scripts working under tcsh or csh only.
Could be something wrong with filesystem or hard disk. Upload full output of "journalctl -b" to https://susepaste.org/
Not knowing how to get access to the site indicated by you, I wrote the output of "journalctl -b" on my own site:
You said "today at 13:00", but logs start today at 17:55. Did you reboot after 13:00? Do you still observe this issue after reboot? There are no obvious errors in log.
On Tue, 14 Jun 2022 at 19:04:25 +0200, Andrei Borzenkov wrote:
On 14.06.2022 19:48, Wolfgang Mueller wrote:
On Tue, 14 Jun 2022 at 17:59:24 +0200, Andrei Borzenkov wrote:
On 14.06.2022 17:57, Wolfgang Mueller wrote:
Today at 13:00 my other computer suddenly became dark in KDE under Leap 15.4, recently installed. Then I opened a console and found out that tcsh does not work any more. I prepared three very simple scripts for testing purposes:
-rwxr-xr-x 1 wolfgang 28 Jun 14 15:41 script.tcsh -rwxr-xr-x 1 wolfgang 27 Jun 14 15:57 script.sh -rwxr-xr-x 1 wolfgang 29 Jun 14 15:45 script.bash
script.tcsh, consists of these 2 lines: #!/bin/csh echo 'Hi, world'
script.sh, consists of these 2 lines: #!/bin/sh echo 'Hi, world
and script.bash, consists of these 2 lines: #!/bin/bash echo 'Hi, world'
Invoking them directly fails, yielding the error messages: script.tcsh: Command not found. script.sh: Command not found. script.bash: Command not found.
Which is expected as current working directory is not in PATH by default.
Obviously.
When I invoke one of them specifying "tcsh", i.e. tcsh-prompt> tcsh script.tcsh the script hangs and has to be dropped with CTRL C. The same for tcsh-prompt> sh script.sh and tcsh-prompt> bash script.bash.
The only way to make the scripts work is invoking them in a bash session. Now bash-prompt> tcsh script.tcsh hangs again, but bash-prompt> sh script.sh and bash-prompt> bash script.bash work correctly, producing the output Hi, world
But even in a bash session, it is not possible to invoke the scripts directly.
Anyway, I urgently need tcsh, having a lot of scripts working under tcsh or csh only.
Could be something wrong with filesystem or hard disk. Upload full output of "journalctl -b" to https://susepaste.org/
Not knowing how to get access to the site indicated by you, I wrote the output of "journalctl -b" on my own site:
You said "today at 13:00", but logs start today at 17:55. Did you reboot after 13:00? Do you still observe this issue after reboot?
I rebooted even twice, but the issue persists.
There are no obvious errors in log.
So, I will have to repeat the installation, I fear. Wolfgang
On 14.06.2022 20:34, Wolfgang Mueller wrote: ...
The only way to make the scripts work is invoking them in a bash session. Now bash-prompt> tcsh script.tcsh hangs again, but ...
You said "today at 13:00", but logs start today at 17:55. Did you reboot after 13:00? Do you still observe this issue after reboot?
I rebooted even twice, but the issue persists.
There are no obvious errors in log.
So, I will have to repeat the installation, I fear.
Can you kill hanging tcsh with ^C? Or with any other signal? Run strace -f -o /tmp/tcsh.log tcsh script.tcsh and provide resulting /tmp/tcsh.log.
On Wed, 15 Jun 2022 at 06:16:28 +0200, Andrei Borzenkov wrote:
On 14.06.2022 20:34, Wolfgang Mueller wrote: ...
The only way to make the scripts work is invoking them in a bash session. Now bash-prompt> tcsh script.tcsh hangs again, but ...
You said "today at 13:00", but logs start today at 17:55. Did you reboot after 13:00? Do you still observe this issue after reboot?
I rebooted even twice, but the issue persists.
There are no obvious errors in log.
So, I will have to repeat the installation, I fear.
Can you kill hanging tcsh with ^C? Or with any other signal?
Not only can I, but I actually have to; otherwise the desktop would remain blocked.
Run strace -f -o /tmp/tcsh.log tcsh script.tcsh
It hangs and has to be killed with ^C. I ran and killed it twice.
and provide resulting /tmp/tcsh.log.
http://www.ariannuccia.de/temp/Borzenkov/tcsh.log.html Thanks again and best regards, Wolfgang
On Wed, Jun 15, 2022 at 9:20 AM Wolfgang Mueller <wm@ariannuccia.de> wrote:
Run strace -f -o /tmp/tcsh.log tcsh script.tcsh
It hangs and has to be killed with ^C. I ran and killed it twice.
and provide resulting /tmp/tcsh.log.
12950 execve("/usr/bin/awk", ["awk", "{if($3==h){while($(++i)!=\"#\")a=$"..., "h=azure", "/etc/hosts.0"], 0x5586df6e4f30 /* 61 vars */) = 0 ... 12950 openat(AT_FDCWD, "/etc/hosts.0", O_RDONLY) = 3 ... 12950 read(3, "# This file describes a number o"..., 3303) = 3303 12950 --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} --- So some tcsh startup file executes awk script that probably loops doing something. Find out where this awk is called from and what it is doing. Maybe this file /etc/hosts.0 is corrupted, do not know. Or maybe you do not need this awk call at all ...
On 2022/06/15 10:14:06 +0300, Andrei Borzenkov wrote:
On Wed, Jun 15, 2022 at 9:20 AM Wolfgang Mueller <wm@ariannuccia.de> wrote:
Run strace -f -o /tmp/tcsh.log tcsh script.tcsh
It hangs and has to be killed with ^C. I ran and killed it twice.
and provide resulting /tmp/tcsh.log.
12950 execve("/usr/bin/awk", ["awk", "{if($3==h){while($(++i)!=\"#\")a=$"..., "h=azure", "/etc/hosts.0"], 0x5586df6e4f30 /* 61 vars */) = 0 ...
12950 openat(AT_FDCWD, "/etc/hosts.0", O_RDONLY) = 3 ...
12950 read(3, "# This file describes a number o"..., 3303) = 3303 12950 --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
So some tcsh startup file executes awk script that probably loops doing something. Find out where this awk is called from and what it is doing. Maybe this file /etc/hosts.0 is corrupted, do not know. Or maybe you do not need this awk call at all ...
Interesting ... currently I do not use awk at login nor setup of the tcsh: /suse/werner> grep awk /etc/csh.* ... only in the complete and .. as expected in gawk.csh an awk is found /suse/werner> grep -l awk /etc/profile.d/*.*csh /etc/profile.d/complete.tcsh /etc/profile.d/gawk.csh /suse/werner> rpm -qf /etc/profile.d/gawk.csh gawk-4.2.1-1.41.x86_64 try to use the -f option tcsh -f script.tcsh and also search for the cause below /etc/profile.d/ in the *.*csh resource scripts ... or in one of your personal (t)csh configuration and/or resource files like ~/.(t)cshrc or ~/.login . Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
On Wed, 15 Jun 2022 at 09:14:06 +0200, Andrei Borzenkov wrote:
On Wed, Jun 15, 2022 at 9:20 AM Wolfgang Mueller <wm@ariannuccia.de> wrote:
Run strace -f -o /tmp/tcsh.log tcsh script.tcsh
It hangs and has to be killed with ^C. I ran and killed it twice.
and provide resulting /tmp/tcsh.log.
12950 execve("/usr/bin/awk", ["awk", "{if($3==h){while($(++i)!=\"#\")a=$"..., "h=azure", "/etc/hosts.0"], 0x5586df6e4f30 /* 61 vars */) = 0 ...
12950 openat(AT_FDCWD, "/etc/hosts.0", O_RDONLY) = 3 ...
12950 read(3, "# This file describes a number o"..., 3303) = 3303 12950 --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} ---
So some tcsh startup file executes awk script that probably loops doing something. Find out where this awk is called from and what it is doing. Maybe this file /etc/hosts.0 is corrupted, do not know. Or maybe you do not need this awk call at all ...
You are right, /etc/hosts.0 was corrupted, such that an awk call to it in /etc/csh.cshrc.local hung in an endless loop. After the appropriate correction of /etc/hosts.0, everything works well again. You have exactly found the error - thank you very very much! Without your help, I don't know how I would have solved my problem. Greetings from Germany, Wolfgang
participants (3)
-
Andrei Borzenkov -
Dr. Werner Fink -
Wolfgang Mueller