can't get past the "Create a new account 1/3" page about twake

[jhjacobs81]

oh! its working now :)

i am actually logged in to my own hosted Twake :)

[iFloris]

@jhjacobs81 hello, I ran into the same issue trying Self-Hosted Twake on Proxmox in a Ubuntu 20 guest. Thanks to your suggestions above I was able to get Twake's ScyllaDB to run in the VM. I changed the cpu type to host in order to expose all possible flags.
I edited the relevant [number].conf in /etc/pve/qemu-server and added cpu: host below cores, saved and restarted the guest.

[RomaricMourgues]

Great for ScyllaDB ! To tell Twake that you don't use ES, follow theses instructions to detach the configuration: https://doc.twake.app/configuration
Then just set es.host to false ("es" => [ "host" => false ])

(And restart everything)

[jhjacobs81]

Thats possibly even a better option! Thanks for sharing. I am glad it worked for you :-);

[RomaricMourgues]

It must be because the Twake backend is not up yet, but you should see a waiting page instead of the login/subscribe screen.
Can you start the docker, refresh the frontend after 1 minute, wait for 10 more minutes and then try to create an account ?

[jhjacobs81]

10 minutes, half an hour.. setting up a new docker instance.. not much is working :(

[RomaricMourgues]

Ok so it may be something else, can you look at the developers console from Chrome and also look at the php logs (docker-compose logs -f --tail 100 php) when trying to subscribe?
Thank you!

[RomaricMourgues]

I think it was a duplicate of #100
Can you just update your Twake installation using this documentation? https://doc.twake.app/installation

[jhjacobs81]

for the time beeing we switched to the free version, but i will test it when i get home!

is there a way to point the clients to the self hosted version?

[RomaricMourgues]

I’m not sure I follow you. I understand you switched to the online web.twake.app version.
What do you want to do with the clients ? (Do you mean frontend client or customers ?)

[jhjacobs81]

yes, i have downloaded the macOS client, and the iOS client. they work for the online version obviously, but if i switch back to the selfhosted variant, and publish it at twake.mydomain.tld, can i then point the clients to twake.mydomain.tld to have them work with my self hosted version?

[RomaricMourgues]

Yes you can, the iOS client has an option to change the server on the login page (bottom of the screen), on MacOS you can find the option in "help" > "Change Twake Server".
The iOS app is young, so you'll not be able yet to receive push notifications from your private installation.

[jhjacobs81]

well, thats okay :) i love helping out as much as i can :) too bad i cant code php :( but i'll pitch in some idea's and maybe help with some bugs, as well as the translation :)

[jhjacobs81]

any chance the macOS version can get a preferences option where one can set the self hosted url as well? :))

[RomaricMourgues]

any chance the macOS version can get a preferences option where one can set the self hosted url as well? :))

Yes: MacOS you can find the option in "help" > "Change Twake Server" :)

well, thats okay :) i love helping out as much as i can :) too bad i cant code php :( but i'll pitch in some idea's and maybe help with some bugs, as well as the translation :)

Thank you :) We'll make things easier in the future for contributors!

[jhjacobs81]

nope, still not working :(
i did exactly what the documentation say, im hosting a debian VM on proxmox but that shouldn't be a problem i think?

[RomaricMourgues]

May be I'm not understanding your problem well:

Is this option available on your frontend client ? You should be able to change the Twake server url and once OK is pressed the app should restart and use your server.

[jhjacobs81]

yes, the client is okay :)

no, i am having a problem with the docker container, i try to use it per documentation, but i never get past this screen:

[RomaricMourgues]

Ok sorry, can you give me the output of docker-compose logs -f --tail 100 scylladb ?

[jhjacobs81]

all the containers are running, except the elasticsearch, i try deleting that

i'll try the logs output, hang on

[jhjacobs81]

docker-compose logs -f --tail 100 scylladb
Attaching to twake_scylladb_1
scylladb_1 | | .++ . |
scylladb_1 | | ..oo |
scylladb_1 | +----[SHA256]-----+
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg="Starting node_exporter (version=0.17.0, branch=HEAD, revision=f6f6194a436b9a63d0439abc585c76b19a206b21)" source="node_exporter.go:82"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg="Build context (go=go1.11.2, user=root@322511e06ced, date=20181130-15:51:33)" source="node_exporter.go:83"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg="Enabled collectors:" source="node_exporter.go:90"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - arp" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - bcache" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - bonding" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - conntrack" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - cpu" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - diskstats" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - edac" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - entropy" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - filefd" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - filesystem" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - hwmon" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - infiniband" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - interrupts" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - ipvs" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - loadavg" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - mdadm" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - meminfo" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - netclass" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - netdev" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - netstat" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - nfs" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - nfsd" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - sockstat" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - stat" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - textfile" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - time" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - timex" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - uname" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - vmstat" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - xfs" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg=" - zfs" source="node_exporter.go:97"
scylladb_1 | time="2020-08-08T18:16:20Z" level=info msg="Listening on :9100" source="node_exporter.go:111"
scylladb_1 | Scylla requires the sse4.2 and clmul instruction sets, check your processor and hypervisor
scylladb_1 | Scylla requires a processor with SSE 4.2 and PCLMUL support
scylladb_1 | 2020-08-08 18:16:21,284 INFO success: scylla entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
scylladb_1 | 2020-08-08 18:16:21,287 INFO success: scylla-housekeeping entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
scylladb_1 | 2020-08-08 18:16:21,288 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
scylladb_1 | 2020-08-08 18:16:21,288 INFO success: scylla-jmx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
scylladb_1 | 2020-08-08 18:16:21,290 INFO exited: scylla (exit status 71; not expected)
scylladb_1 | Connecting to http://localhost:100002020-08-08 18:16:21,639 INFO spawned: 'scylla' with pid 64
scylladb_1 | 2020-08-08 18:16:21,640 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
scylladb_1 | 2020-08-08 18:16:21,640 INFO success: node-exporter entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
scylladb_1 |
scylladb_1 | Starting the JMX server
scylladb_1 | 2020-08-08 18:16:22,642 INFO success: scylla entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
scylladb_1 | Scylla requires the sse4.2 and clmul instruction sets, check your processor and hypervisor
scylladb_1 | Scylla requires a processor with SSE 4.2 and PCLMUL support
scylladb_1 | 2020-08-08 18:16:22,850 INFO exited: scylla (exit status 71; not expected)
scylladb_1 | JMX is enabled to receive remote connections on port: 71992020-08-08 18:16:23,125 INFO spawned: 'scylla' with pid 75
scylladb_1 |
scylladb_1 | Scylla requires the sse4.2 and clmul instruction sets, check your processor and hypervisor
scylladb_1 | Scylla requires a processor with SSE 4.2 and PCLMUL support
scylladb_1 | 2020-08-08 18:16:23,525 INFO exited: scylla (exit status 71; not expected)
scylladb_1 | Generating public/private rsa key pair.
scylladb_1 | Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
=== KEY GENERATION THINGY ===
scylladb_1 | Could not load host key: /etc/ssh/ssh_host_ecdsa_key
scylladb_1 | 2020-08-08 18:16:24,557 INFO spawned: 'scylla' with pid 86
scylladb_1 | Scylla requires the sse4.2 and clmul instruction sets, check your processor and hypervisor
scylladb_1 | Scylla requires a processor with SSE 4.2 and PCLMUL support
scylladb_1 | 2020-08-08 18:16:24,715 INFO exited: scylla (exit status 71; not expected)
scylladb_1 | Traceback (most recent call last):
scylladb_1 | File "/opt/scylladb/scripts/libexec/scylla-housekeeping", line 208, in
scylladb_1 | args.func(args)
scylladb_1 | File "/opt/scylladb/scripts/libexec/scylla-housekeeping", line 134, in check_version
scylladb_1 | current_version = sanitize_version(get_api('/storage_service/scylla_release_version'))
scylladb_1 | File "/opt/scylladb/scripts/libexec/scylla-housekeeping", line 93, in get_api
scylladb_1 | return get_json_from_url("http://" + api_address + path)
scylladb_1 | File "/opt/scylladb/scripts/libexec/scylla-housekeeping", line 88, in get_json_from_url
scylladb_1 | raise RuntimeError(f'Failed to get "{path}" due to the following error: {retval}')
scylladb_1 | RuntimeError: Failed to get "http://localhost:10000/storage_service/scylla_release_version" due to the following error: <urlopen error [Errno 99] Cannot assign requested address>
scylladb_1 | 2020-08-08 18:16:26,786 INFO spawned: 'scylla' with pid 108
scylladb_1 | Scylla requires the sse4.2 and clmul instruction sets, check your processor and hypervisor
scylladb_1 | Scylla requires a processor with SSE 4.2 and PCLMUL support
scylladb_1 | 2020-08-08 18:16:26,934 INFO exited: scylla (exit status 71; not expected)
scylladb_1 | 2020-08-08 18:16:29,939 INFO spawned: 'scylla' with pid 118
scylladb_1 | Scylla requires the sse4.2 and clmul instruction sets, check your processor and hypervisor
scylladb_1 | Scylla requires a processor with SSE 4.2 and PCLMUL support
scylladb_1 | 2020-08-08 18:16:30,093 INFO exited: scylla (exit status 71; not expected)
scylladb_1 | 2020-08-08 18:16:31,094 INFO gave up: scylla entered FATAL state, too many start retries too quickly

Well that gets us somewhere... let me see bout the SSE error thingy

[jhjacobs81]

its beginning to get on my nerves :( i added the ss4.2 instructionset, but it doesnt seem to know about the pclmul instructionset.

no selfhosting twake for me i suppose :(

[RomaricMourgues]

Ok, we never had this error! You're running Twake on "debian VM on proxmox" what kind of machine is it ? It seems your processor isn't compatible with ScyllaDB...
In January we should release our new core which enable the use of other databases, in the meanwhile I need more info on your host machine, I have no idea of what it can be (appart from the fact that ScyllaDB / Cassandra are very hard to install and maintain, this is part of our SaaS history and why we will open our core to other databases)

[jhjacobs81]

i never had an error like that either ;-)

vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz
stepping : 9

i would think thats good enough?

[jhjacobs81]

okay well.. i had to manually add "pclmulqdq" to the cpu flags in my vm config.. and that seems to work so far...

[jhjacobs81]

now i have another thing to solve..

[jhjacobs81]

i dont use es.. i have removed it earlier on because i thought that was the problem 👍

i could begin all over again.. but im not liking es much anyway ;)

[RomaricMourgues]

So sad it took 11 days... We'll continue to make things simplier in the future!
Thank you so much for your time!

[jhjacobs81]

Yeah well.. Microsoft has been making OS'es since 1980 and they still dont have it right.. so i would not worry much just yet :)

imagine that! i could become the world's largest Twake hoster for professionals.. :D

[jhjacobs81]

i'll close this issue now :) hopefully in the future, it could help someone else (i might make blog post about it even)

[objeni]

that file is not present in my VM.

[iFloris]

@objeni /etc/pve/qemu-server/$number.conf is on the VM server, in my case proxmox. If you are running into this problem, with the error Scylla requires a processor with SSE 4.2 and PCLMUL support that means that the VM host does not expose that CPU flag. If you are not using Qemu / KVM / Proxmox or similar, you need to find where to change that setting in your specific environment.

[objeni]

but this issue not in my VM system, it's created in my real machine

[objeni]

can you please tell me the location for this file in the real system

[iFloris]

If you are using Proxmox like me, the conf file you need to edit on the VM host system (real system) is in /etc/qemu-server/. That directory would have one or more files in it such as 100.conf or another number. This corresponds to the VM number in Proxmox.
If you are using another virtualization platform based on Qemu with KVM like openstack, the conf file is going to be named differently.

Alternatively, if you are not using virtualization, and are trying to run Twake on bare metal, that would mean that the machine you are using is not capable of running ScyllaDB. I believe Twake's team is working on an alternative db, so you would simply have to wait in that case until their open source version has that option.

You could also just use the SaaS version of Twake here: https://web.twake.app

[objeni]

I am using ubuntu 18.04 desktop on my machine and I need to try that first in my machine and then I set up it in my real server so I need to resolve first this issue then I am implementing in my real scenario.

[iFloris]

Hello @objeni if I understand correctly, you want to run Twake locally as a test, on bare metal with no additional virtualization layers (besides the docker containers that Twake builds itself).

In that case, you need to check if your local machine is capable of running ScyllaBD, which requires sse4_2 and PCLMUL as a CPU feature.
Try cat /proc/cpuinfo | grep -oE 'pclmul|sse4_2' in a terminal window.
If your machine supports those CPU flags, that command should give you sse4_2 and PCLMUL as an answer like this:

❯ cat /proc/cpuinfo | grep -oE 'pclmul|sse4_2'
sse4_2
pclmul
❯

If it just gives you a new prompt, without sse4_2 or pclmul, your machine is not capable of running ScyllaDB and as such you cannot locally run Twake at this time.

[objeni]

Okay I will check and tell you
Thanks

[dichvuhuuich]

Ok sorry, can you give me the output of docker-compose logs -f --tail 100 scylladb ?

I've have the same issue, log like this, I'm running on VMware ESXi, 6.7.0, 8169922, HP ProLiant DL380 Gen9, Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz. Please help me to fix!

Attaching to twake_scylladb_1 scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - arp" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - bcache" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - bonding" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - conntrack" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - cpu" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - diskstats" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - edac" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - entropy" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - filefd" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - filesystem" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - hwmon" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - infiniband" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - interrupts" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - ipvs" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - loadavg" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - mdadm" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - meminfo" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - netclass" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - netdev" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - netstat" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - nfs" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - nfsd" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - sockstat" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - stat" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - textfile" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - time" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - timex" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - uname" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - vmstat" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - xfs" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg=" - zfs" source="node_exporter.go:97" scylladb_1 | time="2020-12-16T07:52:45Z" level=info msg="Listening on :9100" source="node_exporter.go:111" scylladb_1 | Generating public/private rsa key pair. scylladb_1 | Your identification has been saved in /etc/ssh/ssh_host_rsa_key. scylladb_1 | Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub. scylladb_1 | The key fingerprint is: scylladb_1 | SHA256:HWJozva0cLATEUaw6J8wq5u/U8nsvGZwPhsuqVOPs7s root@7a31d8a714f4 scylladb_1 | The key's randomart image is: scylladb_1 | +---[RSA 4096]----+ scylladb_1 | | .o=. | scylladb_1 | | . o o | scylladb_1 | | . . = o . | scylladb_1 | | . + = o . | scylladb_1 | | +o .B S . | scylladb_1 | | o=*o * . | scylladb_1 | | ..@+ o | scylladb_1 | |.o*.O. | scylladb_1 | |==E@++ | scylladb_1 | +----[SHA256]-----+ scylladb_1 | Could not load host key: /etc/ssh/ssh_host_ecdsa_key scylladb_1 | Scylla version 4.2.1-0.20201108.4fb8ebccff with build-id d19a95fd85a8e7df2928ccd8c729941f263e8adc starting ... scylladb_1 | command used: "/usr/bin/scylla --log-to-syslog 0 --log-to-stdout 1 --default-log-level info --network-stack posix --developer-mode=1 --overprovisioned --listen-address 172.18.0.5 --rpc-address 172.18.0.5 --seed-provider-parameters seeds=172.18.0.5 --experimental=on --blocked-reactor-notify-ms 999999999" scylladb_1 | parsed command line options: [log-to-syslog: 0, log-to-stdout: 1, default-log-level: info, network-stack: posix, developer-mode: 1, overprovisioned, listen-address: 172.18.0.5, rpc-address: 172.18.0.5, seed-provider-parameters: seeds=172.18.0.5, experimental: on, blocked-reactor-notify-ms: 999999999] scylladb_1 | ERROR 2020-12-16 07:52:46,319 [shard 7] seastar - Could not setup Async I/O: Resource temporarily unavailable. The most common cause is not enough request capacity in /proc/sys/fs/aio-max-nr. Try increasing that number or reducing the amount of logical CPUs available for your application scylladb_1 | 2020-12-16 07:52:46,320 INFO success: scylla entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) scylladb_1 | 2020-12-16 07:52:46,321 INFO success: scylla-housekeeping entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) scylladb_1 | 2020-12-16 07:52:46,321 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) scylladb_1 | 2020-12-16 07:52:46,321 INFO success: scylla-jmx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) scylladb_1 | 2020-12-16 07:52:46,321 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) scylladb_1 | 2020-12-16 07:52:46,321 INFO success: node-exporter entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) scylladb_1 | 2020-12-16 07:52:46,414 INFO exited: scylla (exit status 1; not expected) scylladb_1 | Connecting to http://localhost:10000 scylladb_1 | Starting the JMX server scylladb_1 | 2020-12-16 07:52:46,637 INFO spawned: 'scylla' with pid 82 scylladb_1 | Scylla version 4.2.1-0.20201108.4fb8ebccff with build-id d19a95fd85a8e7df2928ccd8c729941f263e8adc starting ... scylladb_1 | command used: "/usr/bin/scylla --log-to-syslog 0 --log-to-stdout 1 --default-log-level info --network-stack posix --developer-mode=1 --overprovisioned --listen-address 172.18.0.5 --rpc-address 172.18.0.5 --seed-provider-parameters seeds=172.18.0.5 --experimental=on --blocked-reactor-notify-ms 999999999" scylladb_1 | parsed command line options: [log-to-syslog: 0, log-to-stdout: 1, default-log-level: info, network-stack: posix, developer-mode: 1, overprovisioned, listen-address: 172.18.0.5, rpc-address: 172.18.0.5, seed-provider-parameters: seeds=172.18.0.5, experimental: on, blocked-reactor-notify-ms: 999999999] scylladb_1 | JMX is enabled to receive remote connections on port: 7199 scylladb_1 | ERROR 2020-12-16 07:52:47,441 [shard 6] seastar - Could not setup Async I/O: Resource temporarily unavailable. The most common cause is not enough request capacity in /proc/sys/fs/aio-max-nr. Try increasing that number or reducing the amount of logical CPUs available for your application scylladb_1 | 2020-12-16 07:52:47,504 INFO exited: scylla (exit status 1; not expected) scylladb_1 | 2020-12-16 07:52:48,508 INFO spawned: 'scylla' with pid 107 scylladb_1 | Scylla version 4.2.1-0.20201108.4fb8ebccff with build-id d19a95fd85a8e7df2928ccd8c729941f263e8adc starting ... scylladb_1 | command used: "/usr/bin/scylla --log-to-syslog 0 --log-to-stdout 1 --default-log-level info --network-stack posix --developer-mode=1 --overprovisioned --listen-address 172.18.0.5 --rpc-address 172.18.0.5 --seed-provider-parameters seeds=172.18.0.5 --experimental=on --blocked-reactor-notify-ms 999999999" scylladb_1 | parsed command line options: [log-to-syslog: 0, log-to-stdout: 1, default-log-level: info, network-stack: posix, developer-mode: 1, overprovisioned, listen-address: 172.18.0.5, rpc-address: 172.18.0.5, seed-provider-parameters: seeds=172.18.0.5, experimental: on, blocked-reactor-notify-ms: 999999999] scylladb_1 | ERROR 2020-12-16 07:52:49,098 [shard 6] seastar - Could not setup Async I/O: Resource temporarily unavailable. The most common cause is not enough request capacity in /proc/sys/fs/aio-max-nr. Try increasing that number or reducing the amount of logical CPUs available for your application scylladb_1 | 2020-12-16 07:52:49,177 INFO exited: scylla (exit status 1; not expected) scylladb_1 | Traceback (most recent call last): scylladb_1 | File "/opt/scylladb/scripts/libexec/scylla-housekeeping", line 208, in <module> scylladb_1 | args.func(args) scylladb_1 | File "/opt/scylladb/scripts/libexec/scylla-housekeeping", line 134, in check_version scylladb_1 | current_version = sanitize_version(get_api('/storage_service/scylla_release_version')) scylladb_1 | File "/opt/scylladb/scripts/libexec/scylla-housekeeping", line 93, in get_api scylladb_1 | return get_json_from_url("http://" + api_address + path) scylladb_1 | File "/opt/scylladb/scripts/libexec/scylla-housekeeping", line 88, in get_json_from_url scylladb_1 | raise RuntimeError(f'Failed to get "{path}" due to the following error: {retval}') scylladb_1 | RuntimeError: Failed to get "http://localhost:10000/storage_service/scylla_release_version" due to the following error: <urlopen error [Errno 99] Cannot assign requested address> scylladb_1 | 2020-12-16 07:52:52,109 INFO spawned: 'scylla' with pid 144 scylladb_1 | Scylla version 4.2.1-0.20201108.4fb8ebccff with build-id d19a95fd85a8e7df2928ccd8c729941f263e8adc starting ... scylladb_1 | command used: "/usr/bin/scylla --log-to-syslog 0 --log-to-stdout 1 --default-log-level info --network-stack posix --developer-mode=1 --overprovisioned --listen-address 172.18.0.5 --rpc-address 172.18.0.5 --seed-provider-parameters seeds=172.18.0.5 --experimental=on --blocked-reactor-notify-ms 999999999" scylladb_1 | parsed command line options: [log-to-syslog: 0, log-to-stdout: 1, default-log-level: info, network-stack: posix, developer-mode: 1, overprovisioned, listen-address: 172.18.0.5, rpc-address: 172.18.0.5, seed-provider-parameters: seeds=172.18.0.5, experimental: on, blocked-reactor-notify-ms: 999999999] scylladb_1 | ERROR 2020-12-16 07:52:52,698 [shard 7] seastar - Could not setup Async I/O: Resource temporarily unavailable. The most common cause is not enough request capacity in /proc/sys/fs/aio-max-nr. Try increasing that number or reducing the amount of logical CPUs available for your application scylladb_1 | ERROR 2020-12-16 07:52:52,698 [shard 2] seastar - Could not setup Async I/O: Resource temporarily unavailable. The most common cause is not enough request capacity in /proc/sys/fs/aio-max-nr. Try increasing that number or reducing the amount of logical CPUs available for your application scylladb_1 | 2020-12-16 07:52:52,742 INFO exited: scylla (exit status 1; not expected) scylladb_1 | 2020-12-16 07:52:55,749 INFO spawned: 'scylla' with pid 168 scylladb_1 | Scylla version 4.2.1-0.20201108.4fb8ebccff with build-id d19a95fd85a8e7df2928ccd8c729941f263e8adc starting ... scylladb_1 | command used: "/usr/bin/scylla --log-to-syslog 0 --log-to-stdout 1 --default-log-level info --network-stack posix --developer-mode=1 --overprovisioned --listen-address 172.18.0.5 --rpc-address 172.18.0.5 --seed-provider-parameters seeds=172.18.0.5 --experimental=on --blocked-reactor-notify-ms 999999999" scylladb_1 | parsed command line options: [log-to-syslog: 0, log-to-stdout: 1, default-log-level: info, network-stack: posix, developer-mode: 1, overprovisioned, listen-address: 172.18.0.5, rpc-address: 172.18.0.5, seed-provider-parameters: seeds=172.18.0.5, experimental: on, blocked-reactor-notify-ms: 999999999] scylladb_1 | ERROR 2020-12-16 07:52:56,291 [shard 3] seastar - Could not setup Async I/O: Resource temporarily unavailable. The most common cause is not enough request capacity in /proc/sys/fs/aio-max-nr. Try increasing that number or reducing the amount of logical CPUs available for your application scylladb_1 | 2020-12-16 07:52:56,347 INFO exited: scylla (exit status 1; not expected) scylladb_1 | 2020-12-16 07:52:57,349 INFO gave up: scylla entered FATAL state, too many start retries too quickly

[dichvuhuuich]

Hello @objeni if I understand correctly, you want to run Twake locally as a test, on bare metal with no additional virtualization layers (besides the docker containers that Twake builds itself).

In that case, you need to check if your local machine is capable of running ScyllaBD, which requires sse4_2 and PCLMUL as a CPU feature.
Try cat /proc/cpuinfo | grep -oE 'pclmul|sse4_2' in a terminal window.
If your machine supports those CPU flags, that command should give you sse4_2 and PCLMUL as an answer like this:

❯ cat /proc/cpuinfo | grep -oE 'pclmul|sse4_2'
sse4_2
pclmul
❯

If it just gives you a new prompt, without sse4_2 or pclmul, your machine is not capable of running ScyllaDB and as such you cannot locally run Twake at this time.

My Machine is ok?

:~/Twake/twake# cat /proc/cpuinfo | grep -oE 'pclmul|sse4_2'
pclmul
sse4_2
pclmul
sse4_2
pclmul
sse4_2
pclmul
sse4_2
pclmul
sse4_2
pclmul
sse4_2
pclmul
sse4_2
pclmul
sse4_2

[objeni]

yes my system is capable for run that.
sometime ago it run but then i update twake then it not working

[DanishRasaliBASF]

Yeah well.. Microsoft has been making OS'es since 1980 and they still dont have it right.. so i would not worry much just yet :)

imagine that! i could become the world's largest Twake hoster for professionals.. :D

Hello, can you assist me in getting Twake up and running? I can't seem to fix this Waiting for DB to start issue.