Getting an error while starting sever

87 views
Skip to first unread message

salonimi...@gmail.com

unread,
Sep 21, 2020, 7:02:53 AM9/21/20
to schedulix
Hi Team,

I am installing schedulix server for one of our client.

While doing server-start , getting the below error-

Exception in thread "main" java.lang.NoClassDefFoundError: de/independit/scheduler/server/repository/TableLoader
        at de.independit.scheduler.server.repository.SDMSRepository.loadTables(SDMSRepository.java:279)
        at de.independit.scheduler.server.repository.SDMSRepository.<init>(SDMSRepository.java:59)
        at de.independit.scheduler.server.Server.createRepository(Server.java:150)
        at de.independit.scheduler.server.Server.serverMain(Server.java:464)
        at de.independit.scheduler.BICServer.main(BICServer.java:144)
Caused by: java.lang.ClassNotFoundException: de.independit.scheduler.server.repository.TableLoader
        at java.net.URLClassLoader$1.run(URLClassLoader.java:360)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:349)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:348)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:430)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:326)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:363)
        ... 5 more

Please help me.

Thank you,
Saloni

Ronald Jeninga

unread,
Sep 21, 2020, 7:32:32 AM9/21/20
to schedulix
Hi Saloni,

for some reason the TableLoader class cannot be found.

How did you install the software so far?
Are you using rpms or are you installing from source?
What is the size of your BICsuite.jar (you can find it in the lib directory of the schedulix tree)?
And what release are you working with?

Sorry for all those questions. Usually the jar file is completely missing or OK. But in your case it seems to be broken.
So I'll have to find out why.

Best regards,

Ronald
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted
Message has been deleted

salonimi...@gmail.com

unread,
Sep 21, 2020, 8:29:40 AM9/21/20
to schedulix
Hi Ronald ,

To answer your questions-

1. How did you install the software so far?
I have done till below steps mentioned-

1.  Installation Schedulix Server

 

Enter the credentials provided by Chenna to install Schedulix server.(If it has a private key attached then while login to putty go on SSH-> Auth -> Browse the private key file(shared by Chenna)

In hosname give opc@IP_Address in putty login.

[Schediulix Server  : UAT : 10.1.244.11 , root/Oracle%2020*.]

To go on root : sudo su – root

To go on schedulix : sudo su – schedulix

To go on oracle : sudo su - oracle

1.   Installing prerequisite

(root) yum update

#to get the newest system software

(root) yum install git

(root) yum groupinstall "Java Platform"

Gave error pkg not exists, we ignored these

(root) yum install gcc gcc-c++

(root) yum install jflex

(root) yum install glibc.i686

(root) yum install make

(root) yum install java-1.6.0-openjdk-devel java-1.7.0-openjdk-devel

(root) yum install eclipse-swt

Gave error pkg not exists, we ignored these

(root) yum install python-devel

Note: Initial installation for schedulix server and schedulix client  or Job server is same. Jobserver does not require  Zope intallation and Db installation

 

 

2.  Installation Schedulix Server

 

1.   Create the user schedulix

 # useradd -d /home/schedulix -m -s /bin/bash -U schedulix

 

We will use /u01/ path instead of home since in our uat /u01 is the home path

useradd -d /u01/schedulix -m -s /bin/bash -U schedulix

 # passwd schedulix

            Note: # denotes root user. Gave the password schedulix123

Once done, login into schedulix server as user schedulix and do the following

(sudo su – schedulix)

 

2.   Create/Upate .bashrc file under schedulix user

we don't need these , these are for our local env to access internet.

# setting proxy for skillnetinc (only use for local server)

export http_proxy=http://wpad.skillnetinc.com:3128

export https_proxy=http://wpad.skillnetinc.com:3128

export ftp_proxy=http://wpad.skillnetinc.com:3128

 

3.   Download of the schedulix source distribution from github.

 

Run this on schedulix user, path /u01/schedulix

git clone https://github.com/schedulix/schedulix.git -b v2.7 schedulix-2.7

Afterwards all the files of the schedulix source distribution will be stored in the subdirectory

 

 $HOME/schedulix-2.7

($HOME : home/schedulix/schedulix-2.7)

 

4.   Set the environment variables. update the following in .bashrc file.

 

Put all the jars in the path given in bashrc file and give permission as chmod 777 to all the files from root user

 

export SDMSHOME=/u01/schedulix/schedulix-2.7

export CLASSPATH=$CLASSPATH:/usr/share/java/jflex.jar:/usr/share/java/java_cup.jar:/usr/share/java/jna.jar:/usr/share/java/mysql-connector-java-5.1.14.jar

export JAVAHOME=/usr/lib/jvm/java-1.7.0-openjdk

export SWTJAR=/usr/lib/java/org.eclipse.swt-3.1.jar

export JNAJAR=/usr/share/java/jna.jar

export BICSUITEHOME=/u01/schedulix/schedulix

export BICSUITECONFIG=/u01/schedulix/schedulix/etc

export PATH=$BICSUITEHOME/bin:$PATH

 

Note:Verify the path in the export path specified.(check the files are there for this specific path)

If files are not there take them from a recent schedulix server and always copy as user root.

You can also take the jars from the below zip

 

 

5.   make, the actual compilation of the system.

If the already compiled version is available no need to create on.

Follow the steps below: (check cd $HOME points to /u01/schedulix)

    cd  $HOME/schedulix-\versionnumber/

    execute the command: export SDMSHOME=`pwd`

            cd $HOME/schedulix-\versionnumber/src

            make

3.  Install MYSQL

 

This will be from root user

1.   Update your system

 

            sudo yum update

            Note: MySQL must be installed from the community repository.

If it throws error proceed to next step.

  2.   Download and add the repository, then update.

 

            wget http://repo.mysql.com/mysql-community-release-el7-5.noarch.rpm

            sudo rpm -ivh mysql-community-release-el7-5.noarch.rpm

            yum update

 

3.   Install MySQL as usual and start the service. 

 

                        sudo yum install mysql-server

                        sudo systemctl start mysqld

 

4.   MySQL Server secure_installation

 

script to address several      security concerns in a default

            MySQL installation.

                        sudo mysql_secure_installation

since we have not set any password for the root in mysql
when it will ask for password just press enter.

                When it asks to set new password give our root password = Oracle%2020*.

You will be given the choice to change the MySQL root password, remove anonymous user accounts, disable root logins outside of localhost, and remove test databases. It is recommended that you answer yes to these options.

 

5.   Create schedulix database

 

login by user schedulix

              $ mysql --user=root -p

              Enter password: Oracle%2020*.

              mysql> create user schedulix identified by 'schedulix';

              mysql> create database schedulixdb;

              mysql> grant all on schedulixdb.* to schedulix;

              mysql> quit

 

 

Go to the directory: /u01/schedulix/schedulix-2.7/sql and execute the following command – login by root

   #mysql --user=schedulix --password=schedulix --database=schedulixdb --execute="source mysql/install.sql"

              Note: Give appropriate password

              (E.g.                 mysql --user=schedulix --password=schedulix --database=schedulixdb           --execute="source mysql/install.sql")

Login with root user into MySQL and execute the following commands:

              CREATE USER 'schedulix'@'localhost' IDENTIFIED BY 'schedulix';

              CREATE USER 'schedulix'@'snsl-vm-19' IDENTIFIED BY 'schedulix';

Give schedulix server name instead of 'snsl-vm-19’

 

CREATE USER 'schedulix'@'storehubapptst9.pepeganga.net' IDENTIFIED BY 'schedulix';

For KOMAX-

6.  Installation Schedulix Server-- Continue

 

1.   Create a symbolic link

 

          $ cd $HOME

          $ ln -s schedulix-2.7 schedulix

 

Note: Provide the permissions

(root)cd $HOME (go to home path of schedulix /u01/schedulix)

(root)chmod +r schedulix/ -R

(root)chmod +x schedulix/ -R

2.   Software environment  

            $ cd $BICSUITEHOME/etc

for fff in *.template; do

TRG=`basename $fff .template`;   

cp $fff $BICSUITECONFIG/$TRG;

done

If error comes like this ,” No such file or directory” then export all the paths again.

 

[schedulix@storehubapptst9 etc]$ export SDMSHOME=/u01/schedulix/schedulix-2.7

[schedulix@storehubapptst9 etc]$ export CLASSPATH=$CLASSPATH:/usr/share/java/jflex.jar:/usr/share/java/java_cup.jar:/usr/share/java/jna.jar:/usr/share/java/mysql-connector-java-5.1.14.jar

[schedulix@storehubapptst9 etc]$ export JAVAHOME=/usr/lib/jvm/java-1.7.0-openjdk

[schedulix@storehubapptst9 etc]$ export SWTJAR=/usr/lib/java/org.eclipse.swt-3.1.jar

[schedulix@storehubapptst9 etc]$ export JNAJAR=/usr/share/java/jna.jar

[schedulix@storehubapptst9 etc]$ export BICSUITEHOME=/u01/schedulix/schedulix

[schedulix@storehubapptst9 etc]$ export BICSUITECONFIG=/u01/schedulix/schedulix/etc

[schedulix@storehubapptst9 etc]$ export PATH=$BICSUITEHOME/bin:$PATH

3.   Configure the database connection

 

This should be done as user schedulix.if present as root delete and copy again as user schedulix.

In the $BICSUITECONFIG/server.conf configuration file

DbPasswd=schedulix

            DbUrl=jdbc:mysql://localhost:3306/schedulixdb

            DbUser=schedulix

            Hostname= storehubapptst9.pepeganga.net 

Just change hostname, rest all will be same.

            JdbcDriver=com.mysql.jdbc.Driver

           

4.    Configure the schedulix Java Class Path in java.conf

 

This should be done as user schedulix.if present as root delete and copy again as user schedulix.

$BICSUITECONFIG/java.conf   for JDBC

BICSUITECLASSPATH=$BICSUITEJAR:$JDBCJAR:$JNAJAR:$SWTJAR:/usr/share/java/mysql-connector-java-5.1.14.jar

Note: Download  mysql-connector-java-5.1.14.jar and put in appropriate location. This jar file is available in previosly provided zip

 

5.   Start the server

 

$ server-start


2. Are you using rpms or are you installing from source?
I am installing it from source

3. What is the size of your BICsuite.jar (you can find it in the lib directory of the schedulix tree)?
This is the size of BICSuite.jar
 2160828  BICsuite.jar

4. And what release are you working with?
I am working with 2.7 release

Thank you,
Saloni

Ronald Jeninga

unread,
Sep 21, 2020, 9:11:03 AM9/21/20
to schedulix
Hi Saloni,

it all looks pretty sound.
The only thing that seems odd is the size of the jar file.
On my system it has a size of

[ronald@ocelot lib]$ pwd
/home/ronald/schedulix-2.7/lib
[ronald@ocelot lib]$ ls -l BICsuite.jar
-rw-r--r--. 1 ronald ronald 2188475 11. Feb 2019  BICsuite.jar
[ronald@ocelot lib]$


IOW about 20K more than your jar file.
The TableLoader class file fits perfectly into that "hole":

[ronald@ocelot lib]$ cd ../src/server/repository/
[ronald@ocelot repository]$ ls -l TableLoader.class
-rw-rw-r--. 1 ronald ronald 2997 11. Feb 2019  TableLoader.class

But it's very likely that more is missing.

So let's check the jar file itself.
First of all the number of objects within the jar file is:

[ronald@ocelot repository]$ cd -
/home/ronald/schedulix-2.7/lib
[ronald@ocelot lib]$ jar tvf BICsuite.jar | wc -l
784

And the TableLoader class is contained:

[ronald@ocelot lib]$ jar tvf BICsuite.jar | grep TableLoader
  2997 Mon Feb 11 15:33:12 CET 2019 de/independit/scheduler/server/repository/TableLoader.class

Since I spotted that my last compile is apparently about one and a half year ago, I did another "make new".
This time I definitely used a Java 1.8 (that's the Java release we'll use for schedulix 2.10, the next release).
And as to be expected, the exact numbers are a bit different:

[ronald@ocelot src]$ cd ../lib
[ronald@ocelot lib]$ ls -l
total 2192
-rw-r--r--. 1 ronald ronald 2196295 21. Sep 15:03 BICsuite.jar
-rw-rw-r--. 1 ronald ronald   40345 11. Feb 2019  centos7.spec
-rw-rw-r--. 1 ronald ronald    1881 17. Mai 2016  functions.sh
[ronald@ocelot lib]$ java -version
openjdk version "1.8.0_262"
OpenJDK Runtime Environment (build 1.8.0_262-b10)
OpenJDK 64-Bit Server VM (build 25.262-b10, mixed mode)

But the relevant information remains the same:

[ronald@ocelot lib]$ jar tvf BICsuite.jar | wc -l
784
[ronald@ocelot lib]$ jar tvf BICsuite.jar | grep TableLoader
  3017 Mon Sep 21 15:03:38 CEST 2020 de/independit/scheduler/server/repository/TableLoader.class

If you repeat this on your side, we'll probably find out that the jar file is broken and we'll have to take a look at the build process.

Best regards,

Ronald

salonimi...@gmail.com

unread,
Sep 21, 2020, 12:09:40 PM9/21/20
to schedulix
Hi Ronald,

I performed the mentioned steps and got the below output.

It seems TableLoader class is not there.

[root@qamombatch lib]# pwd
/volumen1/schedulix/schedulix-2.7/lib
[root@qamombatch lib]# ls -l
total 2156
-rwxr-xr-x. 1 schedulix schedulix 2160828 Sep 21 07:58 BICsuite.jar
-rwxrwxr-x. 1 schedulix schedulix   40345 Sep 21 06:27 centos7.spec
-rwxrwxr-x. 1 schedulix schedulix    1881 Sep 21 06:27 functions.sh


[root@qamombatch lib]# cd ../src/server/repository/
[root@qamombatch repository]# ls -l TableLoader.class
ls: cannot access TableLoader.class: No such file or directory

[root@qamombatch repository]# cd -
/volumen1/schedulix/schedulix-2.7/lib

[root@qamombatch lib]# jar tvf BICsuite.jar | wc -l
762


[root@qamombatch lib]# java -version
java version "1.7.0_261"
OpenJDK Runtime Environment (rhel-2.6.22.2.0.1.el7_8-x86_64 u261-b02)
OpenJDK 64-Bit Server VM (build 24.261-b02, mixed mode)

Thank you,
Saloni

Ronald Jeninga

unread,
Sep 21, 2020, 12:39:27 PM9/21/20
to schedulix
Hi Saloni,

well, it shows that 22 objects are missing from the jar file.
And the TableLoader is one of them.

I don't know why this happened. Usually no jar file is produced if something goes wrong.
Could you do a "make new" (instead of the plain "make") and send me the output?

(More in detail:

export CLASSPATH=$CLASSPATH:/usr/share/java/jflex.jar:/usr/share/java/java_cup.jar:/usr/share/java/jna.jar:/usr/share/java/mysql-connector-java-5.1.14.jar
export SDMSHOME=/volumen1/schedulix/schedulix-2.7     # or whatever
export JNAJAR=/usr/share/java/jna.jar
export SWTJAR=/usr/lib/java/org.eclipse.swt-3.1.jar
cd $SDMSHOME/src
make new
)

It'll produce quite a lot of output. And if you think it contains sensitive information, feel free to edit it.
I don't need real internet addresses, as an example. 1.2.3.4 will do just as well. I also don't need passwords or user names.

The Java version you are using doesn't play a role. schedulix 2.7 runs flawlessly with Java 1.7.
I was just to lazy to use Java 1.7 on the machine I'm using at the moment. I would have to install that first.

BTW. are you aware that it's easy to create rpms from the schedulix sources?
On some development machine you'll have to install some extra packages (jna gcc-c++ java-1.7.0-openjdk-devel rpm-build rpm-libs rpmdevtools rpm-sign).
Then, after a successful build, you do a "make rpm" and 7 rpms will be created.
If you want to install below /u01/schedulix instead of /opt/schedulix, the only thing to do is to edit the spec files (below the lib directory) and the pre- and post-scripts (and replace /opt with /u01).
Maybe there are some spots where I assume /opt/schedulx to be the home directory, but I think not.
Hence if you have to repeat such installations, you'd save time and trouble.

Thank you,

Ronald

salonimi...@gmail.com

unread,
Sep 21, 2020, 1:19:02 PM9/21/20
to schedulix
Hi Ronald,

Please find the attached output of "make new".

Thank you,
Saloni
make_output.txt

salonimi...@gmail.com

unread,
Sep 21, 2020, 1:43:59 PM9/21/20
to schedulix
Hi Ronald,

Now I can see TableLoader.class

[root@qamombatch repository]# cd ../src/server/repository/

[root@qamombatch repository]#  ls -l TableLoader.class
-rw-rw-r--. 1 schedulix schedulix 2997 Sep 21 16:58 TableLoader.class
[root@qamombatch repository]# cd /volumen1/schedulix/schedulix-2.7/lib

[root@qamombatch lib]# ls -l
total 2184
-rw-r--r--. 1 schedulix schedulix 2188478 Sep 21 16:59 BICsuite.jar

-rwxrwxr-x. 1 schedulix schedulix   40345 Sep 21 06:27 centos7.spec
-rwxrwxr-x. 1 schedulix schedulix    1881 Sep 21 06:27 functions.sh

[root@qamombatch lib]#  jar tvf BICsuite.jar | wc -l
784

[root@qamombatch lib]# jar tvf BICsuite.jar | grep TableLoader
  2997 Mon Sep 21 16:58:50 GMT 2020 de/independit/scheduler/server/repository/TableLoader.class


If it seems okay to you . Can I again try server-start. Will it work this time??

Thank you,
Saloni

Ronald Jeninga

unread,
Sep 21, 2020, 2:02:25 PM9/21/20
to schedulix
Hi Saloni,

well, as it seems something unclear happened at the initial build.
The first time is always something special.

It should work now and if you count the entries in the jar file (jar tvf BICsuite.jar | wc -l), you should find 784 now.

It is safe to try to start the server.
If it runs (expected outcome), it's fine. It can't break anything.
If it doesn't run, we'll have to dig deeper.

Best regards,

Ronald

salonimi...@gmail.com

unread,
Sep 22, 2020, 12:27:10 AM9/22/20
to schedulix
Hi Ronald,

When I again did server-start, the below log I got and it did not give message as "server started"

INFO    [main]          22 Sep 2020 04:18:33 GMT **************************************************************************
INFO    [main]          22 Sep 2020 04:18:33 GMT Program-Version : 2.7
INFO    [main]          22 Sep 2020 04:18:33 GMT Level : OPEN
INFO    [main]          22 Sep 2020 04:18:33 GMT Manifest-Version : 1.1
INFO    [main]          22 Sep 2020 04:18:33 GMT Company : independIT Integrative Technologies GmbH
INFO    [main]          22 Sep 2020 04:18:33 GMT Created-By : 1.7.0_261 (Oracle Corporation)
INFO    [main]          22 Sep 2020 04:18:33 GMT Copyright : Copyright (c) 2002-2015 independIT Integrative Technologies GmbH
INFO    [main]          22 Sep 2020 04:18:33 GMT Build : dbe1041f3d600bd4f9fcca7f500d6d5fcb924eb4
INFO    [main]          22 Sep 2020 04:18:33 GMT Build-Date : 21.09.2020 16:59
INFO    [main]          22 Sep 2020 04:18:33 GMT **************************************************************************
INFO    [main]          22 Sep 2020 04:18:33 GMT ** BICsuite!Server
INFO    [main]          22 Sep 2020 04:18:33 GMT ** Version 2.7
INFO    [main]          22 Sep 2020 04:18:33 GMT ** Copyright (C) 2000-2002 topIT Informationstechnologie GmbH
INFO    [main]          22 Sep 2020 04:18:33 GMT ** Copyright (C) 2003-2014 independIT Integrative Technologies GmbH
INFO    [main]          22 Sep 2020 04:18:33 GMT **************************************************************************
INFO    [main]          22 Sep 2020 04:18:33 GMT Commandline Start Options:
INFO    [main]          22 Sep 2020 04:18:33 GMT        /volumen1/schedulix/schedulix/etc/server.conf
INFO    [main]          22 Sep 2020 04:18:33 GMT UserThreads=30
INFO    [main]          22 Sep 2020 04:18:33 GMT JdbcDriver=com.mysql.jdbc.Driver
INFO    [main]          22 Sep 2020 04:18:33 GMT ArchiveSMEColumns=ALL
INFO    [main]          22 Sep 2020 04:18:33 GMT TrustStore=/home/bicsuite/etc/certs/srvkeystore
INFO    [main]          22 Sep 2020 04:18:33 GMT TxRetryCount=3
INFO    [main]          22 Sep 2020 04:18:33 GMT SingleServer=true
INFO    [main]          22 Sep 2020 04:18:33 GMT CompatibilityLevel=BASIC
INFO    [main]          22 Sep 2020 04:18:33 GMT History=14400
INFO    [main]          22 Sep 2020 04:18:33 GMT ParameterHandling=liberal
INFO    [main]          22 Sep 2020 04:18:33 GMT ClientAuthentication=true
INFO    [main]          22 Sep 2020 04:18:33 GMT PriorityLowerBound=10
INFO    [main]          22 Sep 2020 04:18:33 GMT ArchiveHierarchyColumns=ALL
INFO    [main]          22 Sep 2020 04:18:33 GMT ServicePort=2505
INFO    [main]          22 Sep 2020 04:18:33 GMT TimerWakeup=30
INFO    [main]          22 Sep 2020 04:18:33 GMT PriorityDelay=1
INFO    [main]          22 Sep 2020 04:18:33 GMT KeyStore=/home/bicsuite/etc/certs/srvkeystore
INFO    [main]          22 Sep 2020 04:18:33 GMT ArchiveAuditColumns=ALL
INFO    [main]          22 Sep 2020 04:18:33 GMT CodePage=latin1
INFO    [main]          22 Sep 2020 04:18:33 GMT DbUrl=jdbc:mysql://localhost:3306/schedulixdb
INFO    [main]          22 Sep 2020 04:18:33 GMT TimerTimeout=10
INFO    [main]          22 Sep 2020 04:18:33 GMT ArchiveDependencyColumns=ALL
INFO    [main]          22 Sep 2020 04:18:33 GMT DbLoaders=2
INFO    [main]          22 Sep 2020 04:18:33 GMT RunMode=PRODUCTION
INFO    [main]          22 Sep 2020 04:18:33 GMT Port=2506
INFO    [main]          22 Sep 2020 04:18:33 GMT CalendarEntries=250
INFO    [main]          22 Sep 2020 04:18:33 GMT TimerHorizon=2
INFO    [main]          22 Sep 2020 04:18:33 GMT HistoryLimit=28800
INFO    [main]          22 Sep 2020 04:18:33 GMT ScheduleWakeup=30
INFO    [main]          22 Sep 2020 04:18:33 GMT DbUser=schedulix
INFO    [main]          22 Sep 2020 04:18:33 GMT ArchiveVariableColumns=ALL
INFO    [main]          22 Sep 2020 04:18:33 GMT MinHistoryCount=0
INFO    [main]          22 Sep 2020 04:18:33 GMT CalendarHorizon=90
INFO    [main]          22 Sep 2020 04:18:33 GMT TimerSuspendLimit=15
INFO    [main]          22 Sep 2020 04:18:33 GMT Hostname=qamombatch
INFO    [main]          22 Sep 2020 04:18:33 GMT WorkerThreads=2
INFO    [main]          22 Sep 2020 04:18:33 GMT DbHistory=0
INFO    [main]          22 Sep 2020 04:18:33 GMT Archive=false
INFO    [main]          22 Sep 2020 04:18:33 GMT TriggerHardLimit=100
INFO    [main]          22 Sep 2020 04:18:33 GMT TriggerSoftLimit=50
INFO    [main]          22 Sep 2020 04:18:33 GMT MaxHistoryCount=0
INFO    [main]          22 Sep 2020 04:18:33 GMT TraceLevel=1
INFO    [main]          22 Sep 2020 04:18:33 GMT ArchiveKillJobColumns=ALL
INFO    [main]          22 Sep 2020 04:18:33 GMT TimerRecalc=1
INFO    [main]          22 Sep 2020 04:18:33 GMT GCWakeup=240
INFO    [main]          22 Sep 2020 04:18:33 GMT SessionTimeout=0
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting ERRORLOG
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting EXPFINALTIME
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting EXPRUNTIME
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting FINISHTIME
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting ISRESTARTABLE
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting JOBID
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting JOBNAME
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting JOBSTATE
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting JOBTAG
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting KEY
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting LOGFILE
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting MASTERID
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting MERGEDSTATE
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting PARENTID
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting PID
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting RERUNSEQ
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting RESOURCETIME
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting RUNNABLETIME
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting SCOPENAME
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting SDMSHOST
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting SDMSPORT
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting SEID
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting STARTTIME
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting STATE
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting SUBMITTIME
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting SYNCTIME
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting SYSDATE
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERBASE
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERBASEID
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERBASEJOBID
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERNAME
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERNEWSTATE
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERORIGIN
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERORIGINID
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERORIGINJOBID
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGEROLDSTATE
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERREASON
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERREASONID
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERREASONJOBID
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERSEQNO
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting TRIGGERTYPE
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting LAST_WARNING
INFO    [main]          22 Sep 2020 04:18:33 GMT Exporting WORKDIR
INFO    [main]          22 Sep 2020 04:18:33 GMT JDBC Driver used : MYSQL-AB JDBC DRIVER
INFO    [main]          22 Sep 2020 04:18:33 GMT Acquire repository lock for 1600748313222
INFO    [main]          22 Sep 2020 04:18:33 GMT Lock Acquisition for 1600748313222 failed
INFO    [main]          22 Sep 2020 04:18:33 GMT Ticket values Read: 1600686842221, 1600748285449
INFO    [main]          22 Sep 2020 04:18:33 GMT ticket deleted .....
INFO    [main]          22 Sep 2020 04:18:33 GMT Acquire repository lock for 1600748313222
INFO    [main]          22 Sep 2020 04:18:33 GMT Starting Renew Ticket Thread
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT TableLoader 0 started
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT TableLoader 1 started
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for RESOURCE_STATE_PROFILE
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for HIERARCHY_INSTANCE
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for SCHEDULING_ENTITY
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 4, Loaded 4 rows for MEMBER
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 1, Loaded 1 rows for SCHEDULE
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 1, Loaded 1 rows for FOLDER
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for RESOURCE_REQ_STATES
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for EXIT_STATE
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for TRIGGER_STATE
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for EXIT_STATE_MAPPING
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for FOOTPRINT
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for SCHEDULED_EVENT
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for RESOURCE_REQUIREMENT
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for INTERVALL
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for DEPENDENCY_INSTANCE
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 1, Loaded 1 rows for SCOPE
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for SCOPE_CONFIG
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for EXIT_STATE_MAPPING_PROFILE
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for EXIT_STATE_PROFILE
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for RESOURCE_STATE_MAPPING
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for IGNORED_DEPENDENCY
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for TRIGGER_DEFINITION
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 1, Loaded 1 rows for SCHEDULING_HIERARCHY
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for OBJECT_COMMENT
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for RUNNABLE_QUEUE
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for DEPENDENCY_STATE
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for KILL_JOB
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for PERSISTENT_VALUE
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for EXIT_STATE_DEFINITION
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for SUBMITTED_ENTITY
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 1, Loaded 1 rows for NAMED_RESOURCE
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for SCOPE_CONFIG_ENVMAPPING
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for PARAMETER_DEFINITION
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for DEPENDENCY_DEFINITION
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for EVENT_PARAMETER
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for ENTITY_VARIABLE
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for RESSOURCE
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 3, Loaded 3 rows for USERS
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for EVENT
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for NAMED_ENVIRONMENT
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for RESOURCE_STATE
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for RESOURCE_VARIABLE
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 2, Loaded 2 rows for GROUPS
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for SME_COUNTER
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for NICE_PROFILE_ENTRY
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for TRIGGER_QUEUE
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for GRANTS
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for RESOURCE_ALLOCATION
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for CALENDAR
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for RESOURCE_STATE_DEFINITION
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for RESOURCE_STATE_MAP_PROF
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for INTERVAL_HIERARCHY
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for NICE_PROFILE
INFO    [Thread-1]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for INTERVAL_SELECTION
INFO    [Thread-0]      22 Sep 2020 04:18:33 GMT Read 0, Loaded 0 rows for ENVIRONMENT
INFO    [main]          22 Sep 2020 04:18:33 GMT Initializing System Threads
INFO    [main]          22 Sep 2020 04:18:33 GMT Starting 3 Worker Threads
INFO    [main]          22 Sep 2020 04:18:33 GMT Starting Init Repository Thread
INFO    [main]          22 Sep 2020 04:18:33 GMT Starting Scheduling Thread
INFO    [main]          22 Sep 2020 04:18:33 GMT Starting Time Scheduling Thread
INFO    [main]          22 Sep 2020 04:18:33 GMT Starting Trigger Thread
INFO    [main]          22 Sep 2020 04:18:33 GMT Starting Garbage Collection Thread
INFO    [main]          22 Sep 2020 04:18:33 GMT Starting Notifier Thread
INFO    [main]          22 Sep 2020 04:18:33 GMT Starting Listener Thread(s)
INFO    [main]          22 Sep 2020 04:18:33 GMT SSL communication Listener disabled
INFO    [main]          22 Sep 2020 04:18:33 GMT -- SDMS -- Server -- Systems -- ready --
INFO    [2,GarbageCollection(Worker0)]  22 Sep 2020 04:18:33 GMT Start Garbage Collect (now = 1600748313845 preserveTime = 864000000)
INFO    [2,GarbageCollection(Worker0)]  22 Sep 2020 04:18:33 GMT End Garbage Collect
ERROR   [TicketThread]  22 Sep 2020 04:19:05 GMT Error while setting Ticket (no rows updated)
ERROR   [TicketThread]  22 Sep 2020 04:19:05 GMT ****************** Start Stacktrace *********************
ERROR   [TicketThread]  22 Sep 2020 04:19:05 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:140)
ERROR   [TicketThread]  22 Sep 2020 04:19:05 GMT de.independit.scheduler.server.exception.FatalException.<init>(FatalException.java:52)
ERROR   [TicketThread]  22 Sep 2020 04:19:05 GMT de.independit.scheduler.server.RenewTicketThread.renewTicket(RenewTicketThread.java:286)
ERROR   [TicketThread]  22 Sep 2020 04:19:05 GMT de.independit.scheduler.server.RenewTicketThread.SDMSrun(RenewTicketThread.java:302)
ERROR   [TicketThread]  22 Sep 2020 04:19:05 GMT de.independit.scheduler.server.util.SDMSThread.run(SDMSThread.java:197)
ERROR   [TicketThread]  22 Sep 2020 04:19:05 GMT ****************** End Stacktrace   *********************
FATAL   [TicketThread]  22 Sep 2020 04:19:05 GMT Error occurred : Error while setting Ticket (no rows updated)
FATAL   [TicketThread]  22 Sep 2020 04:19:05 GMT ****************** Start Stacktrace *********************
FATAL   [TicketThread]  22 Sep 2020 04:19:05 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:140)
FATAL   [TicketThread]  22 Sep 2020 04:19:05 GMT de.independit.scheduler.server.RenewTicketThread.SDMSrun(RenewTicketThread.java:315)
FATAL   [TicketThread]  22 Sep 2020 04:19:05 GMT de.independit.scheduler.server.util.SDMSThread.run(SDMSThread.java:197)
FATAL   [TicketThread]  22 Sep 2020 04:19:05 GMT ****************** End Stacktrace   *********************
INFO    [Shutdown]      22 Sep 2020 04:19:05 GMT ***********************************************
INFO    [Shutdown]      22 Sep 2020 04:19:05 GMT **                                           **
INFO    [Shutdown]      22 Sep 2020 04:19:05 GMT ** U N G R A C E F U L   S H U T D O W N ! ! **
INFO    [Shutdown]      22 Sep 2020 04:19:05 GMT **                                           **
INFO    [Shutdown]      22 Sep 2020 04:19:05 GMT ***********************************************
INFO    [Shutdown]      22 Sep 2020 04:19:05 GMT Release repository lock from 1600686842221
ERROR   [Shutdown]      22 Sep 2020 04:19:56 GMT Error while unlocking repository
ERROR   [Shutdown]      22 Sep 2020 04:19:56 GMT ****************** Start Stacktrace *********************
ERROR   [Shutdown]      22 Sep 2020 04:19:56 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:140)
ERROR   [Shutdown]      22 Sep 2020 04:19:56 GMT de.independit.scheduler.server.ShutdownThread.SDMSrun(ShutdownThread.java:102)
ERROR   [Shutdown]      22 Sep 2020 04:19:56 GMT de.independit.scheduler.server.util.SDMSThread.run(SDMSThread.java:197)
ERROR   [Shutdown]      22 Sep 2020 04:19:56 GMT ****************** End Stacktrace   *********************
INFO    [Shutdown]      22 Sep 2020 04:19:56 GMT Shutdown completed


Let me know what could be wrong.

Thank you,
Saloni

Ronald Jeninga

unread,
Sep 22, 2020, 3:44:12 AM9/22/20
to schedulix
Hi Saloni,

well, we've made some progress. The server starts, loads the data from the database and reports a

INFO    [main]          22 Sep 2020 04:18:33 GMT -- SDMS -- Server -- Systems -- ready --

That message marks the end of the startup phase.
But then there is this problem (half a minute later) that the server can't set its ticket.
(This is a logic that protects the repository against multiple concurrent schedulix servers that want to work with the repository; not being able to set the ticket is therefor regarded a fatal error)

Initially it finds an active ticket and deletes this because the SingleServer property is set to true.
It then creates its own ticket and starts loading the data from the database:

INFO    [main]          22 Sep 2020 04:18:33 GMT JDBC Driver used : MYSQL-AB JDBC DRIVER
INFO    [main]          22 Sep 2020 04:18:33 GMT Acquire repository lock for 1600748313222
INFO    [main]          22 Sep 2020 04:18:33 GMT Lock Acquisition for 1600748313222 failed
INFO    [main]          22 Sep 2020 04:18:33 GMT Ticket values Read: 1600686842221, 1600748285449
INFO    [main]          22 Sep 2020 04:18:33 GMT ticket deleted .....
INFO    [main]          22 Sep 2020 04:18:33 GMT Acquire repository lock for 1600748313222

About 30 seconds later it detects a problem with the ticket.

The most likely cause for this behavior is another server process that tries to start as well.
Remember that the schedulix server processes are started through scrolllog.
The scrolllog process takes care of the logging, but it is a watchdog too.
If the process it wanted to start exits with an exit code unequal zero, it will restart the process immediately.

You've tried to start a server that couldn't load the TableLoader class and abended.
If you didn't kill the process pair (scrolllog and java), scrolllog will persistently try to start the server.
After the successful build of the jar file this attempt succeeds all of a sudden.

What to do now?
First of all we need to get rid of those quarreling servers. In fact they are playing ping-pong with the repository and effectively doing nothing.
Hence if you do a "ps -fu schedulix" you'll get a list of all schedulix processes that are running, like

[ronald@ocelot schedulix-2.7]$ ps -fu schedulix
UID        PID  PPID  C STIME TTY          TIME CMD
schedul+  2245     1  0 Aug31 ?        00:00:00 scrolllog /opt/schedulix/log/zope.out -e /opt/schedulix/schedulixweb/bin/runzope
schedul+  2246  2245  0 Aug31 ?        00:00:16 /opt/schedulix/software/Zope/bin/python /opt/schedulix/software/Zope/bin/runzope -C /opt/schedulix/schedulixweb/etc/zope.conf
schedul+  2317     1  0 Aug31 ?        00:00:00 /opt/schedulix/schedulix/bin/scrolllog /opt/schedulix/log/localhost.out -e /usr/lib/jvm/java-1.8.0-openjdk/bin/java -client -XX:ParallelGCThreads=2 -cp /opt/schedulix/schedulix
schedul+  2322  2317  0 Aug31 ?        01:02:48 /usr/lib/jvm/java-1.8.0-openjdk/bin/java -client -XX:ParallelGCThreads=2 -cp /opt/schedulix/schedulix/lib/BICsuite.jar:/usr/share/java/postgresql-jdbc.jar:/usr/share/java/jna.jar:
schedul+  2347     1  0 Aug31 ?        00:00:00 /opt/schedulix/schedulix/bin/scrolllog /opt/schedulix/log/host_1.out -e /usr/lib/jvm/java-1.8.0-openjdk/bin/java -client -XX:ParallelGCThreads=2 -cp /opt/schedulix/schedulix
schedul+  2348  2347  0 Aug31 ?        01:04:22 /usr/lib/jvm/java-1.8.0-openjdk/bin/java -client -XX:ParallelGCThreads=2 -cp /opt/schedulix/schedulix/lib/BICsuite.jar:/usr/share/java/postgresql-jdbc.jar:/usr/share/java/jna.jar:
schedul+  2376     1  0 Aug31 ?        00:00:00 /opt/schedulix/schedulix/bin/scrolllog /opt/schedulix/log/host_2.out -e /usr/lib/jvm/java-1.8.0-openjdk/bin/java -client -XX:ParallelGCThreads=2 -cp /opt/schedulix/schedulix
schedul+  2377  2376  0 Aug31 ?        01:04:24 /usr/lib/jvm/java-1.8.0-openjdk/bin/java -client -XX:ParallelGCThreads=2 -cp /opt/schedulix/schedulix/lib/BICsuite.jar:/usr/share/java/postgresql-jdbc.jar:/usr/share/java/jna.jar:
schedul+  2655     1  0 Aug31 ?        00:07:19 /opt/schedulix/schedulix/bin/scrolllog /opt/schedulix/log/BICserver.out -s 50 -l 250000 -o /opt/schedulix/log/BICserver.pid -e /usr/lib/jvm/java-1.8.0-openjdk/bin/java -Xmx10240m
schedul+  2657  2655  0 Aug31 ?        04:14:48 /usr/lib/jvm/java-1.8.0-openjdk/bin/java -Xmx10240m -Xms5120m -XX:NewSize=1280m -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:CMSInitiatingOccupancyFraction=80


You probably don't have any agents running which will make the output a bit shorter.
But you'll have (my hypothesis) find two scrolllog processes and two Java child processes.
And since we'd like to have a cleanly running system, you kill both.

In my example above it is the process with pid 2655 (scrolllog) and 2657 (Java) that run the server.
A "kill -KILL 2655 2657" would clean up the situation.

After getting rid of the servers, a "server-start" should work without issues.

HTH

Best regards,

Ronald

salonimi...@gmail.com

unread,
Sep 22, 2020, 6:51:45 AM9/22/20
to schedulix
Hi Ronald,

Thank you for the help. I am able to start the server. After that I perform the below mentioned steps but I am not able to launch the Zope Quickstart page.

1.   Create the file .sdmshrc under schedulix $HOME

 

$ cat ˜/.sdmshrc Or vi  .sdmshrc

User=SYSTEM

Password=G0H0ME

Host=localhost

Port=2506

Timeout=0

 

2.   Install the convenience package.

The convenience package installs a commonly used configuration for an exit state model.

                        $sdmsh < $BICSUITEHOME/install/convenience.sdms

1.  Installation Zope Server Introduction

A Zope Application Server has to be installed before you can use the schedulixinterface.

Installation

IF easy_install is not available in the server, please execute

# yum install python-setuptools (with root user)

# yum provides easy_install (with root user)

1.    Install virtualenv

All steps to be done as root

                        #yum install python-pip

                         #/bin/python -m pip install --upgrade pip

                         #copy the below tar (virtualenv-16.0.0.tar) in the sever say in /home/opc path

                         #/bin/python -m pip install --user /home/opc/virtualenv-16.0.0.tar

                         # pip install virtualenv-16.0.0.tar.gz

                          #sudo /usr/bin/easy_install virtualenv

2.   Create a virtual Python environment for the Zope installation         (Now execute rest with schedulix user)

 

                        $ mkdir $HOME/software

                        $ cd $HOME/software

                        $ virtualenv --no-site-packages Zope

 

3.   Install the Zope2 software

 

As schedulix user

$ cd $HOME/software/Zope

 

get the file: zope_requirements-2.13.26.txt from any environment from path  /u01/schedulix/schedulix/etc

place this file into my schedulix 2.7 folder under the path: /u01/schedulix/schedulix/etc. File is also attached below

 

go to the path: $HOME/software/Zope (/u01/schedulix/software/Zope ) and execute:

 

/bin/pip install -r /u01/schedulix/schedulix/etc/zope_requirements-2.13.26.txt

 

Create a pkgs directory in software folder(/u01/schedulix/software) and execute(at path /u01/schedulix/software/Zope) to download required packages:

 

 /bin/pip download -d ../pkgs -r /u01/schedulix/schedulix/etc/zope_requirements-2.13.26.txt

 

Execute below commands to manually install few packages:

/bin/pip install ../pkgs/PasteDeploy-1.3.4.tar.gz

/bin/pip install ../pkgs/Paste-1.7.5.1.tar.gz

/bin/pip install ../pkgs/PasteScript-1.7.5.tar.gz

 

 

Finally execute:

/bin/pip install -r ../../schedulix/etc/zope_requirements-2.13.26.txt --no-index -f /opt/schedulix/software/pkgs

 

           

4.   Create a Zope instance for schedulix user interface

 

            $ cd $HOME/software/Zope/bin

$ mkzopeinstance -d $HOME/schedulixweb -u sdmsadm:sdmsadm_password

           

You can use any password of your choice.

 

5.   The Zope server is start/stop briefly for testing

             $HOME/schedulixweb/bin/zopectl start

            In the web browser, the URL http://132.145.150.196:8080

http://132.145.150.196:8080-This URL is not opening

Please help me.

Thank you,
Saloni

salonimi...@gmail.com

unread,
Sep 22, 2020, 7:02:26 AM9/22/20
to schedulix
Hi Ronald,

I am able to launch URL. The port was not open .

Thank you,
Saloni

Ronald Jeninga

unread,
Sep 22, 2020, 7:26:14 AM9/22/20
to schedulix
Hi Saloni,

glad you've been able to figure out yourself what went wrong.
Forgetting about the firewall is one of my favorites as well. (I'm getting better, a bit ;-)

Don't hesitate to ask if you encounter more problems.
I won't be able to answer instantly, but I'm doing my very best.

Best regards,

Ronald
Reply all
Reply to author
Forward
0 new messages