Native xds-server installation fails for REVISION=FunkyFlounder

Description

openSUSE 15.0

RELEASE: FunkyFlounder

http://docs.automotivelinux.org/docs/devguides/en/dev/reference/xds/part-1/1-3_install-xds-server-native.html

Fails at step http://docs.automotivelinux.org/docs/devguides/en/dev/reference/xds/part-1/1-3_install-xds-server-native.html#startstop-xds-server

# systemctl --user status xds-server.service
Failed to connect to bus: Operation not permitted

Instructions wrong or missing step.

Environment

None

Attachments

18 Dec 2018, 10:50 PM

Activity

Sebastien Douheret
July 30, 2019 at 1:21 PM

Cannot reproduce on my side.

Feel free to re-open if you encounter this bug again.

Jan-Simon Moeller
December 18, 2018 at 10:55 PM
(edited)

Well as native did not work yesterday I tried docker, yes. As far as I can see docker is off.

dl9pf@monster:~> docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

dl9pf@monster:~> docker images
REPOSITORY                                      TAG                 IMAGE ID            CREATED             SIZE
docker.automotivelinux.org/agl/worker-generic   6.90.0-139          bb60d7f79100        5 weeks ago         1.62GB

Jan-Simon Moeller
December 18, 2018 at 10:54 PM

Seems like rerunning it fixed the dbus issue.

I'm still on the same host, no reboot, just uninstalling and reinstalling.

dl9pf@monster:~> cat > test.go
package main
import (
    "os/user"
    "fmt"
    "log"
)
func main() {
    usr, err := user.Current()
    if err != nil {
        log.Fatal( err )
    }
    fmt.Println( usr.HomeDir )
}
dl9pf@monster:~> 
dl9pf@monster:~> go run test.go 
/home/dl9pf
dl9pf@monster:~>

Sebastien Douheret
December 18, 2018 at 10:53 PM

Did you mixed native and docker install on the same host ?
By mixing, I mean follow install instructions of one method (eg. native) and then follow instructions of the other method (eg. docker)

Jan-Simon Moeller
December 18, 2018 at 10:47 PM

Log looks fine now.

dl9pf@monster:/tmp/xds-server/logs> cat xds-server.log 
time="2018-12-18T23:15:11+01:00" level=info msg="Logging file: /tmp/xds-server/logs/xds-server.log
" 
time="2018-12-18T23:15:11+01:00" level=info msg="Logging file for HTTP requests:  /tmp/xds-server/logs/xds-server-verbose.log
" 
time="2018-12-18T23:15:11+01:00" level=info msg="Starting Syncthing..." 
time="2018-12-18T23:15:11+01:00" level=info msg=" ST home=/home/dl9pf/.xds/server/syncthing-config" 
time="2018-12-18T23:15:11+01:00" level=info msg=" ST  url=http://localhost:8385" 
time="2018-12-18T23:15:11+01:00" level=info msg="Syncthing started (PID 28789)
" 
time="2018-12-18T23:15:11+01:00" level=info msg="Starting Syncthing-inotify..." 
time="2018-12-18T23:15:11+01:00" level=info msg=" STI  url=http://localhost:8385" 
time="2018-12-18T23:15:11+01:00" level=info msg="syncthing-inotify uses apikey=fAxWq7xYcUUEMrwjiaXZSmcHssgus6GP" 
time="2018-12-18T23:15:11+01:00" level=info msg="Syncthing-inotify started (PID 28791)
" 
time="2018-12-18T23:15:11+01:00" level=info msg="Establishing connection with Syncthing...
" 
time="2018-12-18T23:15:13+01:00" level=info msg="Event monitoring running..." 
time="2018-12-18T23:15:13+01:00" level=info msg="Use folder config file: /home/dl9pf/.xds/server/server-config_folders.xml" 
time="2018-12-18T23:15:13+01:00" level=info msg="Retrieve syncthing folder config" 
time="2018-12-18T23:15:13+01:00" level=error msg="Cannot load syncthing config: no valid device found" 
time="2018-12-18T23:15:13+01:00" level=info msg="Loading initial folders config: 0 folders found" 
time="2018-12-18T23:15:13+01:00" level=info msg="SDK scripts dir: /opt/AGL/xds/server/sdks" 
time="2018-12-18T23:15:14+01:00" level=debug msg="Cross SDKs: 57 defined, 0 installed" 
time="2018-12-18T23:15:14+01:00" level=info msg="Use target config file: /home/dl9pf/.xds/server/server-config_targets.xml" 
time="2018-12-18T23:15:14+01:00" level=warning msg="No target config file found (/home/dl9pf/.xds/server/server-config_targets.xml)" 
time="2018-12-18T23:15:14+01:00" level=info msg="Loading initial targets config: 0 targets found" 
time="2018-12-18T23:15:14+01:00" level=info msg="Serve WEB app dir: /opt/AGL/xds/server/www" 
time="2018-12-18T23:15:14+01:00" level=info msg="Web Server running on localhost:8000 ...
" 
time="2018-12-18T23:15:14+01:00" level=error msg="listen tcp :8000: bind: address already in use"

Ok, let's purge, reinstall and retry.

dl9pf@monster:/tmp/xds-server/logs> sudo rpm -e agl-app-framework-binder agl-xds-server agl-app-framework-binder-devel 
warning: /etc/default/xds-server saved as /etc/default/xds-server.rpmsave

dl9pf@monster:/tmp/xds-server/logs> sudo zypper in agl-app-framework-binder agl-app-framework-binder-devel agl-xds-server
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
Paketabhängigkeiten werden aufgelöst...Die folgenden 3 NEUEN Pakete werden installiert:
  agl-app-framework-binder agl-app-framework-binder-devel agl-xds-server3 neue Pakete zu installieren.
Gesamtgröße des Downloads: 9,7 MiB. Bereits im Cache gespeichert: 0 B. Nach der Operation werden zusätzlich 33,9 MiB belegt.
Fortfahren? [j/n/...? zeigt alle Optionen] (j): 
Paket agl-app-framework-binder-6.0.0-lp150.3.1.x86_64 abrufen                                                                                                                  (1/3), 250,1 KiB (833,4 KiB entpackt)
Abrufen: agl-app-framework-binder-6.0.0-lp150.3.1.x86_64.rpm ...............................................................................................................................................[fertig]
Paket agl-xds-server-6.0.0.1gd99fa40-lp150.5.1.x86_64 abrufen                                                                                                                  (2/3),   9,4 MiB ( 32,9 MiB entpackt)
Abrufen: agl-xds-server-6.0.0.1gd99fa40-lp150.5.1.x86_64.rpm ...................................................................................................................................[fertig (3,0 MiB/s)]
Paket agl-app-framework-binder-devel-6.0.0-lp150.3.1.x86_64 abrufen                                                                                                            (3/3),  41,0 KiB (224,0 KiB entpackt)
Abrufen: agl-app-framework-binder-devel-6.0.0-lp150.3.1.x86_64.rpm .........................................................................................................................................[fertig]
Überprüfung auf Dateikonflikte läuft: ......................................................................................................................................................................[fertig]
(1/3) Installieren: agl-app-framework-binder-6.0.0-lp150.3.1.x86_64 ........................................................................................................................................[fertig]
(2/3) Installieren: agl-xds-server-6.0.0.1gd99fa40-lp150.5.1.x86_64 ........................................................................................................................................[fertig]
(3/3) Installieren: agl-app-framework-binder-devel-6.0.0-lp150.3.1.x86_64 ..................................................................................................................................[fertig]
dl9pf@monster:/tmp/xds-server/logs> sudo mcedit /etc/default/xds-server dl9pf@monster:/tmp/xds-server/logs> systemctl --user status xds-server.service
● xds-server.service - XDS Server
   Loaded: loaded (/usr/lib/systemd/user/xds-server.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2018-12-18 23:15:16 CET; 4min 31s ago
  Process: 28780 ExecStart=/opt/AGL/bin/xds-server (code=exited, status=157)
 Main PID: 28780 (code=exited, status=157)
dl9pf@monster:/tmp/xds-server/logs> systemctl --user stop xds-server.service
dl9pf@monster:/tmp/xds-server/logs> systemctl --user start xds-server.service
Job for xds-server.service failed because the control process exited with error code.
See "systemctl --user status xds-server.service" and "journalctl --user -xe" for details.
dl9pf@monster:/tmp/xds-server/logs> systemctl --user status xds-server.service
● xds-server.service - XDS Server
   Loaded: loaded (/usr/lib/systemd/user/xds-server.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2018-12-18 23:15:16 CET; 4min 59s ago
  Process: 28780 ExecStart=/opt/AGL/bin/xds-server (code=exited, status=157)
 Main PID: 28780 (code=exited, status=157)
dl9pf@monster:/tmp/xds-server/logs> journalctl --user -xe
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
No journal files were opened due to insufficient permissions.

dl9pf@monster:/tmp/xds-server/logs> systemctl --user --unit=xds-server.service --output=cat
systemctl: Unbekannte Option »--unit=xds-server.service«


But it works after another

systemctl --user restart xds-server.service
 

Now I'm puzzled.

Resize issue view side panel

Cannot Reproduce

Details

Assignee

Sebastien Douheret

Reporter

Jan-Simon Moeller

Labels

Contract ID

Components

App Framework

Affects versions

Flounder

Priority

Major

Created December 9, 2018 at 10:37 PM

Updated July 30, 2019 at 6:41 PM

Resolved July 30, 2019 at 1:21 PM

Native xds-server installation fails for REVISION=FunkyFlounder

Description

Environment

Attachments

Activity

Sebastien Douheret
July 30, 2019 at 1:21 PM

Jan-Simon Moeller
December 18, 2018 at 10:55 PM
(edited)

Jan-Simon Moeller
December 18, 2018 at 10:54 PM

Sebastien Douheret
December 18, 2018 at 10:53 PM

Jan-Simon Moeller
December 18, 2018 at 10:47 PM

Details

Assignee

Reporter

Labels

Contract ID

Components

Affects versions

Priority

Flag notifications

Something's gone wrong

Something's gone wrong

Native xds-server installation fails for REVISION=FunkyFlounder

Description

Environment

Attachments

Activity

Sebastien Douheret July 30, 2019 at 1:21 PM

Jan-Simon Moeller December 18, 2018 at 10:55 PM(edited)

Jan-Simon Moeller December 18, 2018 at 10:54 PM

Sebastien Douheret December 18, 2018 at 10:53 PM

Jan-Simon Moeller December 18, 2018 at 10:47 PM

Details

Assignee

Reporter

Labels

Contract ID

Components

Affects versions

Priority

Flag notifications

Something's gone wrong

Something's gone wrong

Sebastien Douheret
July 30, 2019 at 1:21 PM

Jan-Simon Moeller
December 18, 2018 at 10:55 PM
(edited)

Jan-Simon Moeller
December 18, 2018 at 10:54 PM

Sebastien Douheret
December 18, 2018 at 10:53 PM

Jan-Simon Moeller
December 18, 2018 at 10:47 PM