build/run from source, can't bring scylla-server/jmx up

[Jack]

Hi,

I was building scylla from source and was able to get scylla running by using ./build/release/scylla --max-io-requests=256. By looking at the std output, it seems fine all the way and last activity was listening on RPC port.

The issue is I need to use nodetool but I cannot bring scylla-server and scylla-jmx up, e.g., by doing sudo systemctl start scylla-server(scylla-jmx).

Could anyone help? Thanks.

A bit more info: I built and ran scylla release 2.1.rc3 on Ubuntu16.04 with g++-7 and boost163.

The logs from journalctl is as following.

sudo journalctl -u scylla-jmx.service -xe --since "2018-02-13 18:26:00"

-- Logs begin at Mon 2018-02-12 18:21:21 MST, end at Tue 2018-02-13 18:28:12 MST. --

Feb 13 18:26:39 xxx.net systemd[1]: Dependency failed for Scylla JMX.

-- Subject: Unit scylla-jmx.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- 

-- Unit scylla-jmx.service has failed.

-- 

-- The result is dependency.

sudo journalctl -u scylla-server.service -xe --since "2018-02-13 18:26:00"

-- Logs begin at Mon 2018-02-12 18:21:21 MST, end at Tue 2018-02-13 18:29:39 MST. --

Feb 13 18:26:37 xxx.net systemd[1]: Starting Scylla Server...

-- Subject: Unit scylla-server.service has begun start-up

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- 

-- Unit scylla-server.service has begun starting up.

Feb 13 18:26:37 xxx.net scylla_prepare[16082]: tuning /sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host0/target0:0:0/0:0:0:0/block/sda/sda1

Feb 13 18:26:37 xxx.net scylla_prepare[16082]: tuning /sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host0/target0:0:0/0:0:0:0/block/sda

Feb 13 18:26:37 xxx.net scylla_prepare[16082]: already tuned: /sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host0/target0:0:0/0:0:0:0/block/sda/queue/scheduler

Feb 13 18:26:37 xxx.net scylla_prepare[16082]: already tuned: /sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host0/target0:0:0/0:0:0:0/block/sda/queue/nomerges

Feb 13 18:26:37 xxx.net scylla_prepare[16082]: tuning /sys/devices/pci0000:00/0000:00:02.0/0000:03:00.0/host0/target0:0:0/0:0:0:0/block/sda/sda1

Feb 13 18:26:39 xxx.net scylla[16087]: Scylla version 2.1.rc3-0.20180207.b98d5b3 starting ...

Feb 13 18:26:39 xxx.net scylla[16087]:  [shard 0] init - Could not start Prometheus API server on 0.0.0.0:9180: std::system_error (error system:98, Address a

lready in use)

Feb 13 18:26:39 xxx.net scylla[16087]:  [shard 0] seastar - Exiting on unhandled exception: std::system_error (error system:98, Address already in use)

Feb 13 18:26:39 xxx.net systemd[1]: scylla-server.service: Main process exited, code=killed, status=11/SEGV

Feb 13 18:26:39 xxx.net systemd[1]: Failed to start Scylla Server.

-- Subject: Unit scylla-server.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- 

-- Unit scylla-server.service has failed.

-- 

-- The result is failed.

[Dor Laor]

You received an address already in use error. Use netstat -an | grep 9180 

to figure out who holds it. Could it be that Scylla runs there already?

--
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-users+unsubscribe@googlegroups.com.
To post to this group, send email to scylladb-users@googlegroups.com.
Visit this group at https://groups.google.com/group/scylladb-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/aad4b48e-77be-4a02-bb62-adc3335bd21c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[haonan.lv@gmail.com]

Hi Dor,

Thanks for that! my bad, there was a scylla instance running on background.

Now I have a question, it seems bringing up jmx tries to automatically bring up scylla-server.service first? Because scylla-server failed to run, jmx also failed with "failed on a dependency" message. Can I have jmx run without scylla-server up, e.g., running scylla with command ./build/release/scylla?

The reason I ask is running scylla-server.service needs to run some setup scripts first, e.g., scylla_io_setup, which does some sanity check like on free disk space. I'm running scylla on some shared machines and I have limited disk quota, and always fail those checks. I could modify the setuo scripts but I prefer not messing with it if there's other way around.

To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.
To post to this group, send email to scyllad...@googlegroups.com.

[haonan.lv@gmail.com]

nvm, I happened to make it work by modifying the execute script of scylla-jmx.