user3772108's questions

I try to make a init.d script which should start this java command:

java -cp ./:/opt/glassfish/domains/domain1/lib/*:/opt/glassfish/lib/* com.name.it.svcimpl.OrderRequestDispatcher &

With & it starts as background process and this is fine. The problems are starting when you are trying to get it to the foreground:

[1] 10119
user@server:$ fg 10119
-bash: fg: 10119: no such job

After you are pressing enter this happens:

[1]+  Stopped                 java -cp ./:/opt/glassfish/domains/domain1/lib/*:/opt/glassfish/lib/* name.alcar.it.svcimpl.OrderRequestDispatcher

As you see there was no process like 10119 so why does it stop? But the things getting much more difficult when the command is in a init.d bash script:

#!/bin/bash
(cd /opt/glassfish/domains/domain1/applications/AS/WEB-INF/classes; java -cp ./:/opt/glassfish/domains/domain1/lib/*:/opt/glassfish/lib/* com.name.it.svcimpl.OrderRequestDispatcher &)

(Need to started under the path /opt/glassfish/domains/domain1/applications/AS/WEB-INF/classes)

Now my question as not java programmer is:

• Is it possible to run a java program in background with the option to foreground it from any terminal session?

As you can read it is really important to run it in background. Any user that are logged in should be able to put it to the foreground. The users are connecting with SSH to the terminal.

I try to get a bash script running that should output the java process information to a file. Unfortunately when I add it to the crontab -e the script is not executed.

As user root the script is located in /root/bin

#!/bin/bash
PATH=/bin
DATE=`date +%Y-%m-%d" "%H:%M`
PROCESSINFO=`ps aux | grep java | grep -v grep`

echo "$DATE $PROCESSINFO" >> java.log

This is the crontab -e configuration

* * * * * /root/jobs/log-crush-ftp-process.sh
* * * * * printf "test\n"

The printf "test\n" is just a test, but since the output will only go in the mail there is no result on the screen. What am I missing?

Also I have another question about Java processes. Since everything is running in a runtime enviroment, is there a command where I can get more detailed information about the processes inside the JVM?

EDIT:

I deleted the last line printf... and now I get mails for the script. But still no output in the java.log.

I try to create a init.d service script for the glassfish software. But it seems like my understandings in the LSB init.d guidelines are not the best.

This are the commmands the script should do:

/opt/glassfish/bin/asadmin start-domain
/opt/glassfish/bin/asadmin stop-domain
/opt/glassfish/bin/asadmin restart-domain

My script looks like this but it didn't work. This is my first try to make a init.d script. Please tell me when I do something wrong.

Note: Please look my updated script below EDIT:

#!/bin/sh
#
### BEGIN INIT INFO
#
# Provides:     glassfish
# Required-Start:   $local_fs $remote_fs $network
# Required-Stop:    $local_fs $remote_fs $network
# Default-Start:    2 3 4 5
# Default-Stop:     0 1 6
# Short-Description:    Glassfish scipt (Non official)
# Description:  Start Glassfish domain as service.
#       Non official startup script.
#
### END INIT INFO

BASE=/opt/glassfish/bin
DEAMON=${BASE}/asadmin
USERID=root
NAME=glassfish
DESC="Glassfish domain service"
# PID file for the deamon
PIDFILE=/var/run/glassfish.pid
SCRIPTNAME=/etc/init.d/$NAME

# Exit if the package is not installed
[ -x "$DEAMON" ] || exit 0

# Using LSB functions to perform the operations
. /lib/lsb/init-functions

do_start()
{
    start-stop-deamon --start --quiet --pidfile $PIDFILE --exec $DEAMON start-domain -- $NAME_OPTIONS
}

do_stop()
{
    start-stop-deamon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --exec $DEAMON stop-domain
}

case $1 in
    start)
        if init_is_upstart; then
            exit 1
        fi
        log_deamon_msg "Starting $DESC"
        do_start
        case "$?" in
            0) sendsigs_omit 
               log_end_msg 0 ;;
            1) log_progress_msg "already started"
               log_end_msg 0 ;;
            *) log_end_msg 1 ;;
        esac

        ;;
    stop)
        if init_is_upstart; then
            exit 0
        fi
        log_deamon_msg "Stopping $DESC"
        do_stop
        case "$?" in
            0) log_end_msg 0 ;;
            1) log_progress_msg "already stopped"
               log_end_msg 0 ;;
            *) log_emd_msg 1 ;;
        esac

        ;;
    restart|force-reload)
        if init_is_upstart; then
            exit 1
        fi
        $0 stop
        $0 start
        ;;
    status)
        status_of_proc -p $PIDFILE $DEAMON && exit 0 || exit $?
        ;;
    *)
        echo "Usage: $SCRIPTNAME {start|stop|restart|status}" >&2
        exit 3
        ;;
esac

:       

When I do a '/bin/bash -x ./glassfish status' this is the output:

+ case "$FANCYTTY" in
+ true
++ /usr/bin/tput setaf 1
+ RED=''
++ /usr/bin/tput op
+ NORMAL=''
+ echo ' *  is not running'
 *  is not running
+ return 3
+ exit 3

But it doesn't matter if I do a start or stop. The result is always the same. The script doesn't start the glassfish domain server. Without script everything works fine.

EDIT:

I changed the script to this:

#!/bin/sh

### BEGIN INIT INFO
#
# Provides:     glassfish
# Required-Start:   $local_fs $remote_fs $network
# Required-Stop:    $local_fs $remote_fs $network
# Default-Start:    2 3 4 5
# Default-Stop:     0 1 6
# Short-Description:    Glassfish scipt (Non official)
# Description:  Start Glassfish domain as service.
#       Non official startup script
#
### END INIT INFO

# Using the LSB functions to perform the operations
. /lib/lsb/init-functions

BASE=/opt/glassfish/bin
NAME=glassfish
DAEMON=${BASE}/asadmin
SCRIPTNAME=/etc/init.d/$NAME

#PID file for the daemon
PIDFILE=/var/run/glassfish.pid

#If the daemon is not there, then exit
[ -x "$DAEMON" ] || exit 5

do_start()
{
    start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON start-domain
}

do_stop()
{
    start-stop-daemon --stop --quiet --pidfile $PIDFILE
}

case $1 in
    start)
        #Check PID file
        if [ -e $PIDFILE ]; then
            status_of_proc -p $PIDFILE $DAEMON "$NAME process" && status="0" || status="$?"
            # IF SUCCESS dont start again
            if [ $status = "0" ]; then
                exit
            fi
        fi

        #Start the daemon
        log_daemon_msg "Starting the process" "$NAME"
        if do_start; then
            log_end_msg 0
        else
            log_end_msg 1
        fi
        ;;

    stop)
        # Stop the daemon
        if [ -e $PIDFILE ]; then
            status_of_proc -p $PIDFILE $DAEMON "Stopping the $NAME process" && status="0" || status="$?"
            if [ "$status" = 0]; then
                do_stop
            fi
        else
            log_daemon_msg "$NAME process is not running"
            log_end_msg 0
        fi
        ;;

    restart)
        # Restart the daemon
            $0 stop && sleep 2 && $0 start
        ;;

    status)
        # Check status
        if [ -e $PIDFILE ]; then
            status_of_proc -p $PIDFILE $DAEMON "$NAME process" && exit 0 || exit $?
        else
            log_daemon_msg "$NAME Process is not running"
            log_end_msg 0
        fi
        ;;

    *)
        # Show help
        echo "Usage: $SCRIPTNAME {start|stop|restart}" >&2
        exit 3
        ;;
esac

After the change the output is this:

 * Starting the process glassfish                                                                                                                                                                                                            Waiting for domain1 to start .........
Successfully started the domain : domain1
domain  Location: /opt/glassfish/domains/domain1
Log File: /opt/glassfish/domains/domain1/logs/server.log
Admin Port: 4848
Command start-domain executed successfully.

It can start the process now. Then the next problem appears when stopping the service:

 * glassfish process is not running

But the process is running and the script does not even try and just abort. There is also no glassfish PID file under /var/run.

I misstyped and entered this command.

sudo chmod -R -755 /usr/local/nagios/libexec/*

Now it seems like the normal user "nagios" can not see any files in this folder. But the user is owner and the rights on 777.

drwxr-xr-x  2 nagios nagios 4096 Apr 30 17:43 libexec

But when I try to execute the file:

/usr/local/nagios/libexec/check_nrpe
-bash: /usr/local/nagios/libexec/check_nrpe: No such file or directory

The file did have this rights:

-rwxrwxrwx 1 nagios nagios  63845 Apr 30 17:43 check_nrpe

Hi tried to add my nagios service to the runlevel 1-5 (or at least 2). But when I used the command

sudo update-rc.d nagios default

I received the error

update-rc.d: warning: /etc/init.d/nagios missing LSB keyword 'default-start'

update-rc.d: warning: /etc/init.d/nagios missing LSB keyword 'default-stop'

usage: update-rc.d [-n] [-f] <basename> remove
   update-rc.d [-n] <basename> defaults [NN | SS KK]
   update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] .
   update-rc.d [-n] <basename> disable|enable [S|2|3|4|5]
            -n: not really
            -f: force

The disable|enable API is not stable and might change in the future.

Since there are only symbolic links in the /etc/rc2.d folder my next idea would be to just simple create a symbolic link to the binary. But I am not sure if this is a good idea since there must be a reason for a existing update-rc.d program?

I am using Ubuntu 14.04.

How can I found out which ports a program is using on his execution?

I am using a Ubuntu 14.04 Server and the program "SMcli". But the program shows on every execution "Network errors were detected while connecting to storage system". But before we changed the location everything was working fine.

Now I need to know which ports this program is using. Then I can look which ports the target is listening.