Announcement

**drhtmal** · June 15, 2020, 07:41 AM

08:31:31:5564:[Warning]->Error starting web server, port in use? Are you running a web server on the designated port? Edit settings.ini in the Config folder and change gWebSvrPort=## to a different port #. Address already in use

**mik3** · June 15, 2020, 08:20 AM

Once you shut down the service, check if it's still loaded. Do a ps aux | grep -i go .

Also, move the install out of your /root directory. That's not a good secure practice.

Best to place this in /opt/

**otttech** · June 15, 2020, 08:43 AM

So, out of nowhere this all just started working. Then I moved homeseer to the /opt directory as you suggested and same issue again.

I believe as drhtmal noted the server is already running on the same port is the issue. I think this is because the process is not getting shutdown properly when I call

Code:

systemctl stop hs4

How can I have the service send the "shutdown" command to the HSConsole.exe instance of the service to have HomeSeer properly shutdown? Maybe that will fix this.

**zwolfpack** · June 15, 2020, 10:18 AM

You need to set Working directory in the unit file.

Unit file

Code:

[Unit]
Description=HomeSeer Home Automation
Documentation=https://homeseer.com/support-home/
After=network-online.target remote-fs.target time-sync.target
Before=multi-user.target

[Service]
WorkingDirectory=/opt/HomeSeer
ExecStart=/usr/bin/mono HSConsole.exe --log
SyslogIdentifier=HomeSeer HSx
StandardOutput=null
Restart=on-failure
RestartSec=30
KillMode=none
TimeoutStopSec=300
ExecStop=/opt/HomeSeer/hsstop.sh

[Install]
WantedBy=multi-user.target

Then add this script at /opt/HomeSeer/hsstop.sh to perform the shutdown

Code:

#!/bin/bash
# hsstop.sh - stop the HS application
# supports: systemd service shutdown

# import login credentials used to login to web server
# these are ignored if password not required
inifile=$(dirname $0)/Config/$(basename $0 .sh).ini
login=
test -r $inifile && . $inifile

# extract web server port from settings.ini
hsroot=$(dirname $0)  # where this script lives
webport=$(awk -F= '\
{
    gsub("\015", "") # remove CR character
    if ($1 == "gWebSvrPort") print $2
}
' $hsroot/Config/settings.ini)

# send application shutdown command
for i in $(seq 1 5)
do
    curl -f -s -o /dev/null ${login:+-u} $login --data 'ConfirmShutdownhs=Yes' "
http://localhost:$webport/LinuxTools"
    rc=$?
    test $rc -eq 0 && break
    sleep 2
done

killmain()
{
    test -n "$MAINPID" && kill -0 $MAINPID && kill $MAINPID
}

trap killmain EXIT

# if curl cmd unsuccessful, terminate main process
test $rc -ne 0 && killmain

# wait until all HomeSeer mono processes terminate, with timeout
maxwait=300
polltime=5
mono=$(which mono) || exit
for (( t=0; t<$maxwait; t+=$polltime ))
do
    pgrep -af $mono.'*'\(HSConsole\|HomeSeer\) || break
    sleep $polltime
done

**otttech** · June 15, 2020, 01:48 PM

Thanks zwolfpack!

Those two scripts seemed to do the trick!

The only thing I still see in the Startup.log for HomeSeer though is that it's complaining "HomeSeer was not shut down successfully the previous time it was started." in the Startup.log file.

Everything works fine as far as I can tell, however when the system is shutdown by the service rather than the shutdown command in HomeSeer itself this message results on next startup

**zwolfpack** · June 15, 2020, 02:06 PM

Originally posted by otttech View Post

Everything works fine as far as I can tell, however when the system is shutdown by the service rather than the shutdown command in HomeSeer itself this message results on next startup

The hsstop script is intended to prevent that message. It sends the shutdown command thru the web UI.

Make sure the script is set to be executable:

Code:

sudo chmod +x hsstop.sh

Do you require a password for local access to the web UI?

**otttech** · June 16, 2020, 06:33 AM

zwolfpack,

Originally I thought my original problem was all due to permissions so I chmod 777 the entire homeseer folder, it's still like that and all files are globally executable, same issue.

**k0d3g3ar** · June 16, 2020, 08:11 AM

Did you install Ubuntu 20.04 with a GUI or headless?

K

**drhtmal** · June 16, 2020, 08:45 AM

Originally posted by k0d3g3ar View Post

Did you install Ubuntu 20.04 with a GUI or headless?

K

There is really no need for a GUI if you are just running it as a server.

**otttech** · June 16, 2020, 08:52 AM

Ubuntu is running headless.

Another interesting thing is I created a virtual device. But if I delete it, it is back after restart and it also seems to not accept it's room assignments or floor assignments. I can set them ok and they are there only until I restart.

**zwolfpack** · June 16, 2020, 10:29 AM

Originally posted by otttech View Post

I chmod 777 the entire homeseer folder, it's still like that and all files are globally executable.

That wasn't really necessary nor wise ...

You didn't answer the other question, Do you require a password for local access to the web UI? If so, you need to add a extra config file.

**otttech** · June 16, 2020, 10:39 AM

Well the 777 was basically to.determine if it was a permissions issue. I wanted to see if that resolved it. It doesn't.

No I do not require a local login but it still prompts me for one. I enter nothing and I'm allowed in... How do.we explain that?

**zwolfpack** · June 16, 2020, 10:49 AM

Originally posted by otttech View Post

How do.we explain that?

I don't know, but that could be what's interfering with the shutdown script. It needs to be able to login to do the shutdown.

You can try adding the config file. Create a file in the Config subfolder named hsstop.ini with a single line

Code:

login="username:password"

This username/password is one valid for web login, not the Linux login.

**otttech** · June 16, 2020, 09:47 PM

Still not working. I tried both with login as you mentioned and without. Yes, I did disable local login and added subnets 127.0.0,192.168.0

I just started on HS4 PRO. How bad is this beta? Are we anywhere close to a release? Seems very buggy.

It seems like some config is retained and some is not.

For the life of me I cannot get basics working either. I name the device, give it a Floor and Room name then his Save. On the devices page it shows what I set those values to correctly. Then I go to edit the device again and all those fields are blank and I have to re-enter them. Is this a known issue or is there an issue with my setup in particular?

Seems like basics to me...

Announcement

HS4 4.0.8.0 on Ubuntu Server 20.04 - Startup Service Not Working

HS4 4.0.8.0 on Ubuntu Server 20.04 - Startup Service Not Working

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment