LCS configuration under SLES 11

[Florian Bilek]

Dear all,

Currently I am running Hercules under Ubuntu 8.10. My configuration works
fine. There is a LCS defined to z/VM. This is how the configuration look
like:

--- eth0 (192.168.1.190/24)
     !
     '------ tap0 (192.168.1.191/24) ---> z/VM

In principle this is working well.

Now here my problem:

Already earlier this year I tried to migrate to Ubuntu 9.04 but I couldn't
manage to get the LCS connection to work. Now I tried with SLES 11 and I do
get the same problem.

It seems that the tap0 interface is not fully functioning. In order to avoid
any problems relating from authorization I run Hercules as root.

Hercules reports that it opens the tap0 interface successfully and ifconfig
shows a tap0 interface but no IP address is set on this interface. Hercules
reports that it does not use the default mac address 00:00:00:00:00:00 but
replaces this with the tap0 mac address.

I have checked net.ipv4.conf.all.proxy_arp = 1. The tap0 interface doesn't
get the IP address 192.168.1.191 or anything else.

A tcpdump -i tap0 reports that the network is down.

In Ubuntu 8.10 I get a route entry to 192.168.1.191 gw 0.0.0.0 tap0 while
this is not happening under SLES 11. It is interesting that under Ubuntu
8.10 tap0 does not have an IP V4 address but an IP V6.

An arp -a shows that the address 192.168.1.191 is incomplete pointing to
eth0 adapter and not to tap0.

I have compiled the actual svn version of Hercules and it starts correctly.
Also the IPL of z/VM works without problem.

Any ideas how to solve this? Did somebody successfully run under SLES 11?

--
Kind regards

Florian


[Non-text portions of this message have been removed]

[robert mckennon]

Florian,
   I feel your pain... I tried getting LCS to work on SuSE 11 for about
a week.  And then I ran across a post recommending using SLES10
instead.  So I downloaded 10 and it worked like a champ.  I don't know
if Suse has since fixed the problem in 11 or not, but I couldn't get it
to work.

     I do know that even with SLES 10, I have to wait for it to bring up
the eth0 device on the guest side, before I can assign the IP address to
the host tap0 device.  I don't know if this is normal, but it's the way
I get  it to work.  (I have Hercules running on Slackware 12.)

Hope this helps,

Rob McKennon


Florian Bilek wrote:

>  
>
> Dear all,
>
> Currently I am running Hercules under Ubuntu 8.10. My configuration works
> fine. There is a LCS defined to z/VM. This is how the configuration look
> like:
>
> --- eth0 (192.168.1.190/24)
> !
> '------ tap0 (192.168.1.191/24) ---> z/VM
>
> In principle this is working well.
>
> Now here my problem:
>
> Already earlier this year I tried to migrate to Ubuntu 9.04 but I couldn't
> manage to get the LCS connection to work. Now I tried with SLES 11 and
> I do
> get the same problem.
>
> It seems that the tap0 interface is not fully functioning. In order to
> avoid
> any problems relating from authorization I run Hercules as root.
>
> Hercules reports that it opens the tap0 interface successfully and
> ifconfig
> shows a tap0 interface but no IP address is set on this interface.
> Hercules
> reports that it does not use the default mac address 00:00:00:00:00:00 but
> replaces this with the tap0 mac address.
>
> I have checked net.ipv4.conf.all.proxy_arp = 1. The tap0 interface doesn't
> get the IP address 192.168.1.191 or anything else.
>
> A tcpdump -i tap0 reports that the network is down.
>
> In Ubuntu 8.10 I get a route entry to 192.168.1.191 gw 0.0.0.0 tap0 while
> this is not happening under SLES 11. It is interesting that under Ubuntu
> 8.10 tap0 does not have an IP V4 address but an IP V6.
>
> An arp -a shows that the address 192.168.1.191 is incomplete pointing to
> eth0 adapter and not to tap0.
>
> I have compiled the actual svn version of Hercules and it starts
> correctly.
> Also the IPL of z/VM works without problem.
>
> Any ideas how to solve this? Did somebody successfully run under SLES 11?
>
> --
> Kind regards
>
> Florian
>
> [Non-text portions of this message have been removed]
>
>

[Florian Bilek]

Hi Rob,

Thank you very much indeed for that information. It gives me confirmation that it is not rellay the way I installed Hercules. I did already a lot of tests but I see that in this regard I reach my limits as I don't know about the full range of configuration possibilities of the IP stack. According to me the problems are related to the IP stack of the distribution and the lack of proper description.

I run Ubuntu 8.10 with quite an actiual version of the Linux kernel (2.6.30.5) and this has no impact on Hercules. So I guess it must be something in the way the tun/tap interface is working. Maybe it is only a matter of configuration.

It would be great if we could get some ideas in how to trace thats going on. Hercules does not issue an error message, it thinks everything is ok after opening of the tap device but unfortunately it is not.

Here is some more information I saw:

When I enable the -d parameter, I don't se any incomming activity on the tap device.

An ifconfig tap0 shows the RX counters are increasing but TX stays 0. So packets are vanishing somewhere ;-)

Kind regards,
Florian



--- In hercules-390@..., rob mckennon <robmckennon@...> wrote:

>
> Florian,
>    I feel your pain... I tried getting LCS to work on SuSE 11 for about
> a week.  And then I ran across a post recommending using SLES10
> instead.  So I downloaded 10 and it worked like a champ.  I don't know
> if Suse has since fixed the problem in 11 or not, but I couldn't get it
> to work.
>
>      I do know that even with SLES 10, I have to wait for it to bring up
> the eth0 device on the guest side, before I can assign the IP address to
> the host tap0 device.  I don't know if this is normal, but it's the way
> I get  it to work.  (I have Hercules running on Slackware 12.)
>
> Hope this helps,
>
> Rob McKennon
>
>
> Florian Bilek wrote:
> >  
> >
> > Dear all,
> >
> > Currently I am running Hercules under Ubuntu 8.10. My configuration works
> > fine. There is a LCS defined to z/VM. This is how the configuration look
> > like:
> >
> > --- eth0 (192.168.1.190/24)
> > !
> > '------ tap0 (192.168.1.191/24) ---> z/VM
> >
> > In principle this is working well.
> >
> > Now here my problem:
> >
> > Already earlier this year I tried to migrate to Ubuntu 9.04 but I couldn't
> > manage to get the LCS connection to work. Now I tried with SLES 11 and
> > I do
> > get the same problem.
> >
> > It seems that the tap0 interface is not fully functioning. In order to
> > avoid
> > any problems relating from authorization I run Hercules as root.
> >
> > Hercules reports that it opens the tap0 interface successfully and
> > ifconfig
> > shows a tap0 interface but no IP address is set on this interface.
> > Hercules
> > reports that it does not use the default mac address 00:00:00:00:00:00 but
> > replaces this with the tap0 mac address.
> >
> > I have checked net.ipv4.conf.all.proxy_arp = 1. The tap0 interface doesn't
> > get the IP address 192.168.1.191 or anything else.
> >
> > A tcpdump -i tap0 reports that the network is down.
> >
> > In Ubuntu 8.10 I get a route entry to 192.168.1.191 gw 0.0.0.0 tap0 while
> > this is not happening under SLES 11. It is interesting that under Ubuntu
> > 8.10 tap0 does not have an IP V4 address but an IP V6.
> >
> > An arp -a shows that the address 192.168.1.191 is incomplete pointing to
> > eth0 adapter and not to tap0.
> >
> > I have compiled the actual svn version of Hercules and it starts
> > correctly.
> > Also the IPL of z/VM works without problem.
> >
> > Any ideas how to solve this? Did somebody successfully run under SLES 11?
> >
> > --
> > Kind regards
> >
> > Florian
> >
> > [Non-text portions of this message have been removed]
> >
> >
>

[fish-8]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Fox wrote:

[...]

> Here is some more information I saw:
>
> When I enable the -d parameter, I don't see any incoming
> activity on the tap device.
>
> An ifconfig tap0 shows the RX counters are increasing but
> TX stays 0. So packets are vanishing somewhere ;-)
>
> Kind regards,
> Florian

Hi Florian!

I'm not a *nix person so I can't say whether this will work or not BUT...

Have you tried disabling Checksum Offloading?

I'm not sure where you'd do it (i.e. on your host's real NIC? On your
virtual tuntap NIC? On your guest's NIC? etc) but it might be worth a try as
I *do* happen to know that Hercules networking is very sensitive to such
issues (at least on the Windows side but due to the nature of the issue it's
likely its effect may be felt on the *nix side as well).

Just a thought.

- --
"Fish" (David B. Trout) - fish@...
Fight Spam! Join CAUCE! <http://www.cauce.org/>
7 reasons why HTML email is a bad thing
http://www.georgedillon.com/web/html_email_is_evil.shtml
PGP key fingerprints:
DH/DSS: 9F9B BAB0 BA7F C458 1A89 FE26 48F5 D7F4 C4EE 3E2A
RSA: 6B37 7110 7201 9917 9B0D 99E3 55DB 5D58 FADE 4A52





-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.8.0 (Build 2158)
Charset: us-ascii

wj8DBQFK07GUSPXX9MTuPioRAlkjAJ9xPG353KITOBCqdaZPzmZ4jHK3EQCg8IXW
LNA678P+Kb4TGf9VNuQcBrA=
=xMlK
-----END PGP SIGNATURE-----

[dekel35-2]

--- In hercules-390@..., Florian Bilek <florian.bilek@...> wrote:

> Now here my problem:
>
> Already earlier this year I tried to migrate to Ubuntu 9.04 but I couldn't
> manage to get the LCS connection to work. Now I tried with SLES 11 and I do
> get the same problem.

From my experience with openSUSE (which shares many components with SLES), disabling the firewall and apparmor started the connection working. If this works, you can afterwards fine tune the security definitions.

I would also try running hercules as root, just to see if it make any difference. If so - it might be that some of the components used by hercules (e.g. /dev/tun) are not accessible for the normal work user.

Hope this helps.

Jacob Dekel
http://www.mvsdasd.org
http://www.mvsdasd.org/hercstudio

[Florian Bilek]

Hi Fish,

Thank you very much for your input. I will investigate that.

It must be something that Ubuntu 9.04 and SLES 11 have in common.

Kind regrads,
Florian

--- In hercules-390@..., "Fish" <fish@...> wrote:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Fox wrote:
>
> [...]
> > Here is some more information I saw:
> >
> > When I enable the -d parameter, I don't see any incoming
> > activity on the tap device.
> >
> > An ifconfig tap0 shows the RX counters are increasing but
> > TX stays 0. So packets are vanishing somewhere ;-)
> >
> > Kind regards,
> > Florian
>
> Hi Florian!
>
> I'm not a *nix person so I can't say whether this will work or not BUT...
>
> Have you tried disabling Checksum Offloading?
>
> I'm not sure where you'd do it (i.e. on your host's real NIC? On your
> virtual tuntap NIC? On your guest's NIC? etc) but it might be worth a try as
> I *do* happen to know that Hercules networking is very sensitive to such
> issues (at least on the Windows side but due to the nature of the issue it's
> likely its effect may be felt on the *nix side as well).
>
> Just a thought.
>
> - --
> "Fish" (David B. Trout) - fish@...
> Fight Spam! Join CAUCE! <http://www.cauce.org/>
> 7 reasons why HTML email is a bad thing
> http://www.georgedillon.com/web/html_email_is_evil.shtml
> PGP key fingerprints:
> DH/DSS: 9F9B BAB0 BA7F C458 1A89 FE26 48F5 D7F4 C4EE 3E2A
> RSA: 6B37 7110 7201 9917 9B0D 99E3 55DB 5D58 FADE 4A52
>
>
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP Desktop 9.8.0 (Build 2158)
> Charset: us-ascii
>
> wj8DBQFK07GUSPXX9MTuPioRAlkjAJ9xPG353KITOBCqdaZPzmZ4jHK3EQCg8IXW
> LNA678P+Kb4TGf9VNuQcBrA=
> =xMlK
> -----END PGP SIGNATURE-----
>

[Florian Bilek]

Hi Jacob,

Thank you very much for the info. I have the firewall disabled and also I do run hercules as root in order to avoid the issues with /dev/tun and hercifc.

I thin the usage of udev is used for handling the devices made the configuration of tun/tap more complicated.

I agree with Fish that the network stack is quite sensitive.

According to what I see there is a changed behavior of the IP stack.
E.g. the tap interface gets always a new mac address when it is opened. When I am configuring nothing as mac address in the oat file then Hercules is complaining that the mac address of tap0 is used instead of 00:00:00:00:00:00. When I specify an own mac address then also this is not accepted. It seems that there is always the mac address from tap0 used independently what is coded in the oat file.

So this is quit strange. Also that I get under Ubuntu 8.10 a IPV6 address on tap0 that corresponds to the mac address, while in SLES 11 nothing is happening at all. So I don't know how to debug the issue.

Kind regards,
Florian

Kind regards,
Florian
--- In hercules-390@..., "dekel35" <jacob@...> wrote:

>
> --- In hercules-390@..., Florian Bilek <florian.bilek@> wrote:
>
> > Now here my problem:
> >
> > Already earlier this year I tried to migrate to Ubuntu 9.04 but I couldn't
> > manage to get the LCS connection to work. Now I tried with SLES 11 and I do
> > get the same problem.
>
> From my experience with openSUSE (which shares many components with SLES), disabling the firewall and apparmor started the connection working. If this works, you can afterwards fine tune the security definitions.
>
> I would also try running hercules as root, just to see if it make any difference. If so - it might be that some of the components used by hercules (e.g. /dev/tun) are not accessible for the normal work user.
>
> Hope this helps.
>
> Jacob Dekel
> http://www.mvsdasd.org
> http://www.mvsdasd.org/hercstudio
>

[Florian Bilek]

Dear all,

I have checked my configuration and the firewall as well as apparmor are disabled.

However, what I see is when z/VM opens the LCS Hercules would like to start herifc but it doesn't start and resulting in an zombie process. When I stop Hercules, also the zombie process is gone.

Is there a possibility to trace hercifc?

Kind regards,
Florian

--- In hercules-390@..., "dekel35" <jacob@...> wrote:

>
> --- In hercules-390@..., Florian Bilek <florian.bilek@> wrote:
>
> > Now here my problem:
> >
> > Already earlier this year I tried to migrate to Ubuntu 9.04 but I couldn't
> > manage to get the LCS connection to work. Now I tried with SLES 11 and I do
> > get the same problem.
>
> From my experience with openSUSE (which shares many components with SLES), disabling the firewall and apparmor started the connection working. If this works, you can afterwards fine tune the security definitions.
>
> I would also try running hercules as root, just to see if it make any difference. If so - it might be that some of the components used by hercules (e.g. /dev/tun) are not accessible for the normal work user.
>
> Hope this helps.
>
> Jacob Dekel
> http://www.mvsdasd.org
> http://www.mvsdasd.org/hercstudio
>

[dekel35-2]

--- In hercules-390@..., "Fox" <florian.bilek@...> wrote:
> Hercules would like to start herifc but it doesn't start and resulting in an zombie process.

It might be interesting to see the startup log of Hercules. There is a chance that the reason for hercifc crashing is spelled out there.

Also, what is the output of "ls -l <path-to-installation>/hercifc"
(e.g. ls -l /usr/local/bin/hercifc)?

Jacob.
http://www.mvsdasd.org/hercstudio 

[Florian Bilek]

Jacob,

Here is the output from ls -l

-rwsr-x--- 1 root hercules 17803 2009-10-11 16:44 hercifc

The startup of Hercules is without any error messages.

When the TCP/IP stack is starting it opens the LCS and Hercules starts hercifc but under SLES 11 there is only a <defunct> process.

I checked the message log and there is also no error indications visible.

I did also a ccw trace on LCS addresses F00/F01. This shows nothing special.

Kind regards,
Florian




--- In hercules-390@..., "dekel35" <jacob@...> wrote:

>
>
>
> --- In hercules-390@..., "Fox" <florian.bilek@> wrote:
> > Hercules would like to start herifc but it doesn't start and resulting in an zombie process.
>
> It might be interesting to see the startup log of Hercules. There is a chance that the reason for hercifc crashing is spelled out there.
>
> Also, what is the output of "ls -l <path-to-installation>/hercifc"
> (e.g. ls -l /usr/local/bin/hercifc)?
>
> Jacob.
> http://www.mvsdasd.org/hercstudio
>

[George-111]

Florian,
In addition to the mesage log, have a look at the boot.log file. I have
noticed that sometimes messages appear there that are not on the console
or scroll by too quickly to notice them.

George

Fox wrote:

>  
>
> Jacob,
>
> Here is the output from ls -l
>
> -rwsr-x--- 1 root hercules 17803 2009-10-11 16:44 hercifc
>
> The startup of Hercules is without any error messages.
>
> When the TCP/IP stack is starting it opens the LCS and Hercules starts
> hercifc but under SLES 11 there is only a <defunct> process.
>
> I checked the message log and there is also no error indications visible.
>
> I did also a ccw trace on LCS addresses F00/F01. This shows nothing
> special.
>
> Kind regards,
> Florian
>
> --- In hercules-390@...
> <mailto:hercules-390%40yahoogroups.com>, "dekel35" <jacob@...> wrote:
>  >
>  >
>  >
>  > --- In hercules-390@...
> <mailto:hercules-390%40yahoogroups.com>, "Fox" <florian.bilek@> wrote:
>  > > Hercules would like to start herifc but it doesn't start and
> resulting in an zombie process.
>  >
>  > It might be interesting to see the startup log of Hercules. There is
> a chance that the reason for hercifc crashing is spelled out there.
>  >
>  > Also, what is the output of "ls -l <path-to-installation>/hercifc"
>  > (e.g. ls -l /usr/local/bin/hercifc)?
>  >
>  > Jacob.
>  > http://www.mvsdasd.org/hercstudio <http://www.mvsdasd.org/hercstudio>
>  >
>
>

[Florian Bilek]

Dear all,

Here is additional information regarding that problem:

in /var/log/boot.msg there is unfortunately no additional message.

I downloaded the latest version of Hercules from svn and compiled it.

A ls -l from hercifc looks now:

-rwsr-x--- 1 root users 17803 2009-10-18 17:54 hercifc

Here is a ps -ef from the processes:

root     29078  5433  0 18:01 pts/0    00:00:00 /bin/bash /usr/local/bin/iml-hercules
root     29079 29078 21 18:01 pts/0    00:00:40 /opt/sys1/s390/hercules/bin/hercules -f /etc/hercules.cnf -b /opt/sys1/s390/etc/herclogo.txt
root     29137 29079  0 18:02 pts/0    00:00:00 [hercules] <defunct>

There is again this defunct process which should be the hercifc program.

The ifconfig -a looks such as:

hercules:~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:E0:81:B5:14:D1
          inet addr:192.168.1.190  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:81ff:feb5:14d1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10597 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14767 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4573600 (4.3 Mb)  TX bytes:2931645 (2.7 Mb)
          Memory:d4000000-d4020000

eth1      Link encap:Ethernet  HWaddr 00:E0:81:B5:14:D0
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Memory:d4020000-d4040000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:100 (100.0 b)  TX bytes:100 (100.0 b)

tap0      Link encap:Ethernet  HWaddr CE:03:12:E9:A8:B0
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:60 (60.0 b)  TX bytes:0 (0.0 b)

Tap0 was generated from hercules start.

Here is the log from starting Hercules and zVM IPL:

18:01:58 Hercules Version 3.06
18:01:58 (c)Copyright 1999-2009 by Roger Bowler, Jan Jaeger, and others
18:01:58 Built on Oct 18 2009 at 17:52:36
18:01:58 Build information:
18:01:58   Modes: S/370 ESA/390 z/Arch
18:01:58   Max CPU Engines: 16
18:01:58   Using setresuid() for setting privileges
18:01:58   Dynamic loading support
18:01:58   Using shared libraries
18:01:58   No External GUI support
18:01:58   HTTP Server support
18:01:58   Regular Expressions support
18:01:58   Automatic Operator support
18:01:58   National Language Support
18:01:58   Machine dependent assists: cmpxchg1 cmpxchg4 cmpxchg8
18:01:58 Running on hercules Linux-2.6.27.29-0.1-defau.#1 SMP 2009-08-15 17:53:59 +0200 x86_64 MP=8
18:01:58 HHCHD018I Loadable module directory is /opt/sys1/s390/herc111002/lib/hercules
18:01:58 Crypto module loaded (c) Copyright Bernard van der Helm, 2003-2009
18:01:58   Active: Message Security Assist
18:01:58           Message Security Assist Extension 1
18:01:58           Message Security Assist Extension 2
18:01:58 HHCCF077I Engine 0 set to type 0 (CP)
18:01:58 HHCCF077I Engine 1 set to type 0 (CP)
18:01:58 HHCCF077I Engine 2 set to type 0 (CP)
18:01:58 HHCCF077I Engine 3 set to type 0 (CP)
18:01:58 HHCCF077I Engine 4 set to type 0 (CP)
18:01:58 comp=-1,compparm=-1,ra=6,raq=4,rat=2,wr=6,gcint=10,gcparm=0,nostress=0,
18:01:58        freepend=-1,fsync=0,trace=0,linuxnull=0
18:01:58 HHCHT001I HTTP listener thread started: tid=7F8E4E465950, pid=29079
18:01:58 HHCHT013I Using HTTPROOT directory "/opt/sys1/s390/herc111002/share/hercules/"
18:01:58 HHCHT006I Waiting for HTTP requests on port 8081
18:01:58 HHCCF065I Hercules: tid=7F8E50FDF6F0, pid=29079, pgid=29078, priority=0
18:01:58 HHCTE001I Console connection thread started: tid=7F8E4E159950, pid=29079
18:01:58 HHCTE003I Waiting for console connection on port 3270
18:01:58 HHCLC073I 0F00: TAP device tap0 opened
18:01:58 HHCLC073I 0F02: TAP device tap1 opened
18:01:58 HHCLC073I 0F04: TAP device tap2 opened
18:01:58 HHCTA100I 0700: Now Displays: "        "
18:01:58 HHCTA100I 0701: Now Displays: "        "
18:01:58 HHCDA020I /opt/sys1/s390/dasd/vse003c.160 cyls=3339 heads=15 tracks=50085 trklen=56832
18:01:58 HHCDA020I /opt/sys1/s390/dasd/vse004c.161 cyls=3339 heads=15 tracks=50085 trklen=56832
18:01:58 HHCDA020I /opt/sys1/s390/dasd/LX1002.1002 cyls=10017 heads=15 tracks=150255 trklen=56832
18:01:59 HHCDA020I /opt/sys1/s390/dasd/TDSK01.5100 cyls=10017 heads=15 tracks=150255 trklen=56832
18:01:59 HHCDA020I /opt/sys1/s390/dasd/VMSYS1.5101 cyls=10017 heads=15 tracks=150255 trklen=56832
18:01:59 HHCDA020I /opt/sys1/s390/dasd/VMS19E.5102 cyls=10017 heads=15 tracks=150255 trklen=56832
18:01:59 HHCDA020I /opt/sys1/s390/dasd/VMU002.5200 cyls=10017 heads=15 tracks=150255 trklen=56832
trklen=56832
18:01:59 HHCDA020I /opt/sys1/s390/dasd/540RES.5400 cyls=3339 heads=15 tracks=50085 trklen=56832
18:01:59 HHCDA020I /opt/sys1/s390/dasd/540W01.5401 cyls=3339 heads=15 tracks=50085 trklen=56832
18:01:59 HHCDA020I /opt/sys1/s390/dasd/540W02.5402 cyls=3339 heads=15 tracks=50085 trklen=56832
18:02:00 HHCCP002I CPU0000 thread started: tid=7F8D27FFB950, pid=29079, priority=15
18:02:00 HHCTT002I Timer thread started: tid=7F8D27EFA950, pid=29079, priority=-20
18:02:00 HHCCP003I CPU0000 architecture mode z/Arch
18:02:00 HHCCP002I CPU0001 thread started: tid=7F8D27DF9950, pid=29079, priority=15
18:02:00 HHCCP003I CPU0001 architecture mode z/Arch
18:02:00 HHCCP002I CPU0002 thread started: tid=7F8D27CF8950, pid=29079, priority=15
18:02:00 HHCCP003I CPU0002 architecture mode z/Arch
18:02:00 HHCCP002I CPU0003 thread started: tid=7F8D27BF7950, pid=29079, priority=15
18:02:00 HHCCP003I CPU0003 architecture mode z/Arch
18:02:00 HHCCP002I CPU0004 thread started: tid=7F8D27AF6950, pid=29079, priority=15
18:02:00 HHCCP003I CPU0004 architecture mode z/Arch
18:02:00 HHCCP002I CPU0005 thread started: tid=7F8D279F5950, pid=29079, priority=15
18:02:00 HHCCP003I CPU0005 architecture mode z/Arch
18:02:00 HHCPN001I Control panel thread started: tid=7F8E50FDF6F0, pid=29079
18:02:00 HHCAO001I Hercules Automatic Operator thread started;
18:02:00           tid=7F8D276F2950, pri=0, pid=29079
18:02:09 ipl 5400
18:02:09 HHCCP007I CPU0000 architecture mode set to ESA/390
18:02:09 HHCCD001I Readahead thread 1 started: tid=7F8D275F1950, pid=29079
18:02:09 HHCCD001I Readahead thread 2 started: tid=7F8D274F0950, pid=29079
18:02:09 HHCCD001I Readahead thread 3 started: tid=7F8D273EF950, pid=29079
18:02:10 CPU0000: SIGP Set architecture mode (12) CPU0000, PARM 00000001: CC 0
18:02:10 HHCCP007I CPU0000 architecture mode set to z/Arch
18:02:16 HHCCD002I Writer thread 1 started: tid=7F8D271ED950, pid=29079
18:02:16 HHCCD002I Writer thread 2 started: tid=7F8D270EC950, pid=29079
18:02:16 HHCCD002I Writer thread 3 started: tid=7F8D26FEB950, pid=29079
18:02:16 HHCCD002I Writer thread 4 started: tid=7F8D26EEA950, pid=29079
18:02:16 HHCCD002I Writer thread 5 started: tid=7F8D26DE9950, pid=29079
18:02:16 HHCCD002I Writer thread 6 started: tid=7F8D26CE8950, pid=29079
18:02:16 HHCCD003I Garbage collector thread started: tid=7F8D26BE7950, pid=29079
18:02:16 HHCCD001I Readahead thread 4 started: tid=7F8D26AE6950, pid=29079
18:02:16 HHCCD001I Readahead thread 5 started: tid=7F8D269E5950, pid=29079
18:02:16 HHCCD001I Readahead thread 6 started: tid=7F8D268E4950, pid=29079
18:02:17 18:02:17 z/VM  V5 R4.0  SERVICE LEVEL 0902 (64-BIT)
18:02:17 18:02:17 SYSTEM NUCLEUS CREATED ON 2009-06-27 AT 13:32:22, LOADED FROM 540RES
18:02:17 18:02:17
18:02:17 18:02:17 ****************************************************************
18:02:17 18:02:17 * LICENSED MATERIALS - PROPERTY OF IBM*                        *
18:02:17 18:02:17 *                                                              *
18:02:17 18:02:17 * 5741-A05 (C) COPYRIGHT IBM CORP. 1983, 2008. ALL RIGHTS      *
18:02:17 18:02:17 * RESERVED. US GOVERNMENT USERS RESTRICTED RIGHTS - USE,       *
18:02:17 18:02:17 * DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE     *
18:02:17 18:02:17 * CONTRACT WITH IBM CORP.                                      *
18:02:17 18:02:17 *                                                              *
18:02:17 18:02:17 * * TRADEMARK OF INTERNATIONAL BUSINESS MACHINES.              *
18:02:17 18:02:17 ****************************************************************
18:02:17 18:02:17
18:02:17 18:02:17 HCPZCO6718I Using parm disk 1 on volume 540RES (device 5400).
18:02:17 18:02:17 HCPZCO6718I Parm disk resides on cylinders 39 through 158.
18:02:17 18:02:17 The directory on volume 540RES at address 5400 has been brought online.
18:02:18 18:02:18 HCPWRS2513I
18:02:18 18:02:18 HCPWRS2513I Spool files available      142
18:02:18 18:02:18 HCPWRS2512I Spooling initialization is complete.
18:02:18 CPU0000: SIGP Initial CPU reset (0B) CPU0005, PARM 00000000002F2EE0: CC 0
18:02:18 CPU0000: SIGP Set prefix (0D) CPU0005, PARM 00000000008E4000: CC 0
18:02:18 CPU0000: SIGP Initial CPU reset (0B) CPU0004, PARM 00000000002F2EE0: CC 0
18:02:18 CPU0000: SIGP Set prefix (0D) CPU0004, PARM 00000000008E2000: CC 0
18:02:18 CPU0000: SIGP Initial CPU reset (0B) CPU0003, PARM 00000000002F2EE0: CC 0
18:02:18 CPU0000: SIGP Set prefix (0D) CPU0003, PARM 00000000008E0000: CC 0
18:02:18 CPU0000: SIGP Initial CPU reset (0B) CPU0002, PARM 00000000002F2EE0: CC 0
18:02:18 CPU0000: SIGP Set prefix (0D) CPU0002, PARM 00000000008DE000: CC 0
18:02:18 CPU0000: SIGP Initial CPU reset (0B) CPU0001, PARM 00000000002F2EE0: CC 0
18:02:18 CPU0000: SIGP Set prefix (0D) CPU0001, PARM 00000000008DC000: CC 0
18:02:18 CPU0000: SIGP Initial CPU reset (0B) CPU0001, PARM 000000000000E658: CC 0
18:02:18 CPU0000: SIGP Initial CPU reset (0B) CPU0002, PARM 000000000000E658: CC 0
18:02:18 CPU0000: SIGP Set prefix (0D) CPU0002, PARM 00000000008DE000: CC 0
18:02:18 CPU0000: SIGP Restart (06) CPU0002, PARM 00000000000DBBD0: CC 0
18:02:18 CPU0000: SIGP Restart (06) CPU0002, PARM 0000000000073288: CC 0
18:02:18 CPU0002: SIGP Stop (05) CPU0002, PARM 0000000000000002: CC 2
18:02:18 CPU0000: SIGP Initial CPU reset (0B) CPU0003, PARM 000000000000E658: CC 0
18:02:18 CPU0000: SIGP Set prefix (0D) CPU0003, PARM 00000000008E0000: CC 0
18:02:18 CPU0003: SIGP Stop (05) CPU0003, PARM 0000000000000003: CC 0
18:02:18 CPU0000: SIGP Restart (06) CPU0003, PARM 00000000000DBBD0: CC 0
18:02:18 CPU0000: SIGP Restart (06) CPU0003, PARM 0000000000073288: CC 0
18:02:18 CPU0000: SIGP Initial CPU reset (0B) CPU0004, PARM 000000000000E658: CC 0
18:02:18 CPU0000: SIGP Set prefix (0D) CPU0004, PARM 00000000008E2000: CC 0
18:02:18 CPU0000: SIGP Restart (06) CPU0004, PARM 00000000000DBBD0: CC 0
18:02:18 CPU0004: SIGP Stop (05) CPU0004, PARM 0000000000000004: CC 0
18:02:18 CPU0000: SIGP Restart (06) CPU0004, PARM 0000000000073288: CC 2
18:02:18 CPU0000: SIGP Restart (06) CPU0004, PARM 0000000000073288: CC 0
18:02:18 CPU0000: SIGP Initial CPU reset (0B) CPU0005, PARM 000000000000E658: CC 0
18:02:18 CPU0000: SIGP Set prefix (0D) CPU0005, PARM 00000000008E4000: CC 0
18:02:18 CPU0000: SIGP Restart (06) CPU0005, PARM 00000000000DBBD0: CC 0
18:02:18 CPU0005: SIGP Stop (05) CPU0005, PARM 0000000000000005: CC 0
18:02:18 CPU0000: SIGP Restart (06) CPU0005, PARM 0000000000073288: CC 2
18:02:18 CPU0000: SIGP Restart (06) CPU0005, PARM 0000000000073288: CC 0
18:02:18 18:02:18 DASD 5404 dump unit CP IPL pages 22711
18:02:18 HHCCP040I CPI: System Type: VM       Name: PHOENIX  Sysplex:
18:02:18
18:02:18
18:02:18 HHCCF039W                  PGMPRDOS LICENSED specified.
18:02:18
18:02:18                 A licensed program product operating system is running.
18:02:18                 You are responsible for meeting all conditions of your
18:02:18                                 software licenses.
18:02:18
18:02:18
18:02:18 18:02:18 HCPAAU2700I System gateway PHOENIX identified.
18:02:18 18:02:18 z/VM Version 5 Release 4.0, Service Level 0902 (64-bit),
18:02:18 18:02:18 built on IBM Virtualization Technology
18:02:18 18:02:18 There is no logmsg data
18:02:18 18:02:18 FILES:   NO RDR, 0005 PRT,   NO PUN
18:02:18 18:02:18 LOGON AT 18:02:18 CES SUNDAY 10/18/09
18:02:18 18:02:18 SYSC       LOGON  AS  OPERATOR USERS = 1
18:02:18 18:02:18 HCPIOP952I 4G system storage
18:02:18 18:02:18 FILES: 0000063 RDR, 0000044 PRT,      NO PUN
18:02:18 18:02:18 RDR 000C STARTED     SYSTEM
18:02:18 18:02:18 XAUTOLOG EREP
18:02:18 18:02:18 HCPRSR431E Reader 000C id card missing or invalid
18:02:18 18:02:18 HCPCRC8082I Accounting records are accumulating for userid DISKACNT.
18:02:18 18:02:18 HCPCRC8082I EREP records are accumulating for userid EREP.
18:02:18 18:02:18 Command accepted
18:02:18 18:02:18 XAUTOLOG DISKACNT
18:02:18 18:02:18 AUTO LOGON  ***       EREP     USERS = 2     BY OPERATOR
18:02:18 18:02:18 Command accepted
18:02:18 18:02:18 XAUTOLOG AUTOLOG1
18:02:18 18:02:18 AUTO LOGON  ***       DISKACNT USERS = 3     BY OPERATOR
18:02:18 18:02:18 Command accepted
18:02:18 18:02:18 XAUTOLOG OPERSYMP
18:02:18 18:02:18 Command accepted
18:02:18 18:02:18 AUTO LOGON  ***       AUTOLOG1 USERS = 4     BY OPERATOR
18:02:18 18:02:18 AUTO LOGON  ***       OPERSYMP USERS = 5     BY OPERATOR
18:02:18 18:02:18 HCPCLS6056I XAUTOLOG information for AUTOLOG1: The IPL command is verified by the IPL command processor.
18:02:18 18:02:18 HCPCLS6056I XAUTOLOG information for DISKACNT: The IPL command is verified by the IPL command processor.
18:02:18 18:02:18 HCPCLS6056I XAUTOLOG information for EREP: The IPL command is verified by the IPL command processor.
18:02:18 18:02:18 HCPCLS6056I XAUTOLOG information for OPERSYMP: The IPL command is verified by the IPL command processor.
18:02:20 18:02:20 AUTO LOGON  ***       RACFVM   USERS = 6     BY AUTOLOG1
18:02:20 18:02:20  * MSG FROM OPERSYMP: 2 RECORDING FILE(S), 2 RECORDS, A DISK 01 % FULL
18:02:21 18:02:21  * MSG FROM EREP    : 1 RECORDING FILE(S), 195 RECORDS, A DISK 05 % FULL
18:02:21 18:02:21  * MSG FROM DISKACNT: 25 RECORDING FILE(S), 1046 RECORDS, A DISK 31 % FULL
18:02:21 18:02:21 HCPCRC8064I Recording data retrieval has been started; recording *LOGREC for userid EREP.
18:02:35 HHCLC055I tap0 using MAC CE:03:12:E9:A8:B0
18:02:35 HHCLC056W tap0 NOT using MAC 00:00:00:00:00:00
18:02:38 DVHRLY3886I Hourly processing started; with 0 log
18:02:38 DVHRLY3886I files.
18:02:39 DVHRLY3886I Hourly processing started; with 0 log

[Harold Grovesteen-2]

Is the hercifc program directory in the PATH when you execute Hercules?  
If not, it can't be found and Hercules doesn't really know that because
the problem happens over in the process where hercifc lives.  I had to
do a Linux system call trace to figure that out.

I accidentally deleted your long post, but I recall that hercules was in
/opt/..... This directory needs to be in the PATH.

It's easy to try and see if it makes a difference.  You might have an
entirely different problem.

Harold Grovesteen

George wrote:

>Florian,
>In addition to the mesage log, have a look at the boot.log file. I have
>noticed that sometimes messages appear there that are not on the console
>or scroll by too quickly to notice them.
>
>George
>
>Fox wrote:
>  
>
>>
>>
>>Jacob,
>>
>>Here is the output from ls -l
>>
>>-rwsr-x--- 1 root hercules 17803 2009-10-11 16:44 hercifc
>>
>>The startup of Hercules is without any error messages.
>>
>>When the TCP/IP stack is starting it opens the LCS and Hercules starts
>>hercifc but under SLES 11 there is only a <defunct> process.
>>
>>I checked the message log and there is also no error indications visible.
>>
>>I did also a ccw trace on LCS addresses F00/F01. This shows nothing
>>special.
>>
>>Kind regards,
>>Florian
>>
>>--- In hercules-390@...
>><mailto:hercules-390%40yahoogroups.com>, "dekel35" <jacob@...> wrote:
>> >
>> >
>> >
>> > --- In hercules-390@...
>><mailto:hercules-390%40yahoogroups.com>, "Fox" <florian.bilek@> wrote:
>> > > Hercules would like to start herifc but it doesn't start and
>>resulting in an zombie process.
>> >
>> > It might be interesting to see the startup log of Hercules. There is
>>a chance that the reason for hercifc crashing is spelled out there.
>> >
>> > Also, what is the output of "ls -l <path-to-installation>/hercifc"
>> > (e.g. ls -l /usr/local/bin/hercifc)?
>> >
>> > Jacob.
>> > http://www.mvsdasd.org/hercstudio <http://www.mvsdasd.org/hercstudio>
>> >
>>
>>
>>    
>>
>
>
>------------------------------------
>
>Community email addresses:
>  Post message: hercules-390@...
>  Subscribe:    hercules-390-subscribe@...
>  Unsubscribe:  hercules-390-unsubscribe@...
>  List owner:   hercules-390-owner@...
>
>Files and archives at:
>  http://groups.yahoo.com/group/hercules-390
>
>Get the latest version of Hercules from:
>  http://www.hercules-390.org
>
>Yahoo! Groups Links
>
>
>
>
>  
>

[Florian Bilek]

Harold,

Thanks, that is indeed a good hint!

I think I didn't update the PATH. Under Ubuntu I have the hercules directory in the PATH.  

I will change my config and will check it out.

Keep you informed.

Kind regards,
Florian

--- In hercules-390@..., Harold Grovesteen <h.grovsteen@...> wrote:

>
> Is the hercifc program directory in the PATH when you execute Hercules?  
> If not, it can't be found and Hercules doesn't really know that because
> the problem happens over in the process where hercifc lives.  I had to
> do a Linux system call trace to figure that out.
>
> I accidentally deleted your long post, but I recall that hercules was in
> /opt/..... This directory needs to be in the PATH.
>
> It's easy to try and see if it makes a difference.  You might have an
> entirely different problem.
>
> Harold Grovesteen
>
> George wrote:
>
> >Florian,
> >In addition to the mesage log, have a look at the boot.log file. I have
> >noticed that sometimes messages appear there that are not on the console
> >or scroll by too quickly to notice them.
> >
> >George
> >
> >Fox wrote:
> >  
> >
> >>
> >>
> >>Jacob,
> >>
> >>Here is the output from ls -l
> >>
> >>-rwsr-x--- 1 root hercules 17803 2009-10-11 16:44 hercifc
> >>
> >>The startup of Hercules is without any error messages.
> >>
> >>When the TCP/IP stack is starting it opens the LCS and Hercules starts
> >>hercifc but under SLES 11 there is only a <defunct> process.
> >>
> >>I checked the message log and there is also no error indications visible.
> >>
> >>I did also a ccw trace on LCS addresses F00/F01. This shows nothing
> >>special.
> >>
> >>Kind regards,
> >>Florian
> >>
> >>--- In hercules-390@...
> >><mailto:hercules-390%40yahoogroups.com>, "dekel35" <jacob@> wrote:
> >> >
> >> >
> >> >
> >> > --- In hercules-390@...
> >><mailto:hercules-390%40yahoogroups.com>, "Fox" <florian.bilek@> wrote:
> >> > > Hercules would like to start herifc but it doesn't start and
> >>resulting in an zombie process.
> >> >
> >> > It might be interesting to see the startup log of Hercules. There is
> >>a chance that the reason for hercifc crashing is spelled out there.
> >> >
> >> > Also, what is the output of "ls -l <path-to-installation>/hercifc"
> >> > (e.g. ls -l /usr/local/bin/hercifc)?
> >> >
> >> > Jacob.
> >> > http://www.mvsdasd.org/hercstudio <http://www.mvsdasd.org/hercstudio>
> >> >
> >>
> >>
> >>    
> >>
> >
> >
> >------------------------------------
> >
> >Community email addresses:
> >  Post message: hercules-390@...
> >  Subscribe:    hercules-390-subscribe@...
> >  Unsubscribe:  hercules-390-unsubscribe@...
> >  List owner:   hercules-390-owner@...
> >
> >Files and archives at:
> >  http://groups.yahoo.com/group/hercules-390
> >
> >Get the latest version of Hercules from:
> >  http://www.hercules-390.org
> >
> >Yahoo! Groups Links
> >
> >
> >
> >
> >  
> >
>

[Florian Bilek]

Hello Harold,

Thank you very much. It was as you said.  forgot to add the hercules bin directory to the path. With this applied it worked.

Kind regards,
Florian

--- In hercules-390@..., "Fox" <florian.bilek@...> wrote:

>
> Harold,
>
> Thanks, that is indeed a good hint!
>
> I think I didn't update the PATH. Under Ubuntu I have the hercules directory in the PATH.  
>
> I will change my config and will check it out.
>
> Keep you informed.
>
> Kind regards,
> Florian
>
> --- In hercules-390@..., Harold Grovesteen <h.grovsteen@> wrote:
> >
> > Is the hercifc program directory in the PATH when you execute Hercules?  
> > If not, it can't be found and Hercules doesn't really know that because
> > the problem happens over in the process where hercifc lives.  I had to
> > do a Linux system call trace to figure that out.
> >
> > I accidentally deleted your long post, but I recall that hercules was in
> > /opt/..... This directory needs to be in the PATH.
> >
> > It's easy to try and see if it makes a difference.  You might have an
> > entirely different problem.
> >
> > Harold Grovesteen
> >
> > George wrote:
> >
> > >Florian,
> > >In addition to the mesage log, have a look at the boot.log file. I have
> > >noticed that sometimes messages appear there that are not on the console
> > >or scroll by too quickly to notice them.
> > >
> > >George
> > >
> > >Fox wrote:
> > >  
> > >
> > >>
> > >>
> > >>Jacob,
> > >>
> > >>Here is the output from ls -l
> > >>
> > >>-rwsr-x--- 1 root hercules 17803 2009-10-11 16:44 hercifc
> > >>
> > >>The startup of Hercules is without any error messages.
> > >>
> > >>When the TCP/IP stack is starting it opens the LCS and Hercules starts
> > >>hercifc but under SLES 11 there is only a <defunct> process.
> > >>
> > >>I checked the message log and there is also no error indications visible.
> > >>
> > >>I did also a ccw trace on LCS addresses F00/F01. This shows nothing
> > >>special.
> > >>
> > >>Kind regards,
> > >>Florian
> > >>
> > >>--- In hercules-390@...
> > >><mailto:hercules-390%40yahoogroups.com>, "dekel35" <jacob@> wrote:
> > >> >
> > >> >
> > >> >
> > >> > --- In hercules-390@...
> > >><mailto:hercules-390%40yahoogroups.com>, "Fox" <florian.bilek@> wrote:
> > >> > > Hercules would like to start herifc but it doesn't start and
> > >>resulting in an zombie process.
> > >> >
> > >> > It might be interesting to see the startup log of Hercules. There is
> > >>a chance that the reason for hercifc crashing is spelled out there.
> > >> >
> > >> > Also, what is the output of "ls -l <path-to-installation>/hercifc"
> > >> > (e.g. ls -l /usr/local/bin/hercifc)?
> > >> >
> > >> > Jacob.
> > >> > http://www.mvsdasd.org/hercstudio <http://www.mvsdasd.org/hercstudio>
> > >> >
> > >>
> > >>
> > >>    
> > >>
> > >
> > >
> > >------------------------------------
> > >
> > >Community email addresses:
> > >  Post message: hercules-390@...
> > >  Subscribe:    hercules-390-subscribe@...
> > >  Unsubscribe:  hercules-390-unsubscribe@...
> > >  List owner:   hercules-390-owner@...
> > >
> > >Files and archives at:
> > >  http://groups.yahoo.com/group/hercules-390
> > >
> > >Get the latest version of Hercules from:
> > >  http://www.hercules-390.org
> > >
> > >Yahoo! Groups Links
> > >
> > >
> > >
> > >
> > >  
> > >
> >
>