search

Tokutek / mongo

TokuMX is a high-performance, concurrent, compressing, drop-in replacement engine for MongoDB | Issue tracker: https://tokutek.atlassian.net/browse/MX/ |
http://www.tokutek.com/products/tokumx-for-mongodb/
704 stars 97 forks source link

Tokumx not starting after enabling fastUpdates #1204

Closed alberto1el closed 9 years ago

alberto1el commented 9 years ago

I installed TokuMX Community Edition to test the Fast Updates functionality, in a clean Ubuntu 12.04.4 installation (VirtualBox VM, 64bit, 1GB Ram, 2 Virtual processors), without MongoDB installed.

As soon as the installation ended I edited sudo vim /etc/tokumx.conf And added fastUpdates = true saved and sudo service tokumx restart tokumx stop/waiting tokumx start/running, process 11380 after that I try to go to the console, but am not able: mongo TokuMX mongo shell v2.0.0-mongodb-2.4.10 connecting to: test Mon Oct 6 20:36:54.462 Error: couldn't connect to server 127.0.0.1:27017 at /data/package-deb-ubuntu-precise/build/tokumx-2.0.0/src/mongo/shell/mongo.js:145 exception: connect failed

In: /var/logs/tokumx/tokumx.log I get nothing after the stopping of tokumx, in conclusion the service is not starting again, because of the FastUpdates parameter I added, if I remove it I am able to start tokumx again. Mon Oct 6 20:36:40.196 [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends Mon Oct 6 20:36:40.196 [signalProcessingThread] aborting any live transactions Mon Oct 6 20:36:40.196 [signalProcessingThread] now exiting Mon Oct 6 20:36:40.196 dbexit: Mon Oct 6 20:36:40.196 [signalProcessingThread] shutdown: going to close listening sockets... Mon Oct 6 20:36:40.197 [signalProcessingThread] closing listening socket: 16 Mon Oct 6 20:36:40.197 [signalProcessingThread] closing listening socket: 18 Mon Oct 6 20:36:40.197 [signalProcessingThread] closing listening socket: 21 Mon Oct 6 20:36:40.197 [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock Mon Oct 6 20:36:40.197 [signalProcessingThread] shutdown: going to flush diaglog... Mon Oct 6 20:36:40.197 [signalProcessingThread] shutdown: going to close sockets... Mon Oct 6 20:36:40.197 [signalProcessingThread] shutdown: going to close databases... Mon Oct 6 20:36:40.200 [signalProcessingThread] shutdown: going to unload all plugins... Mon Oct 6 20:36:40.200 [signalProcessingThread] shutdown: going to shutdown TokuMX... Mon Oct 6 20:36:40.200 [signalProcessingThread] [tokumx] shutdown Mon Oct 6 20:36:40.329 [signalProcessingThread] shutdown: removing fs lock... Mon Oct 6 20:36:40.329 dbexit: really exiting now

Maybe I am setting the parameter in the wrong file?

leifwalsh commented 9 years ago

The parameter is "setParameter=fastUpdates=true", and please use JIRA in the future, the github issues tracker is no longer in use. https://tokutek.atlassian.net/browse/MX

Sent from my iPhone

On Oct 6, 2014, at 16:45, Alberto notifications@github.com wrote:

I installed TokuMX Community Edition to test the Fast Updates functionality, in a clean Ubuntu 12.04.4 installation (VirtualBox VM, 64bit, 1GB Ram, 2 Virtual processors), without MongoDB installed.

As soon as the installation ended I edited sudo vim /etc/tokumx.conf And added fastUpdates = true saved and sudo service tokumx restart tokumx stop/waiting tokumx start/running, process 11380 after that I try to go to the console, but am not able: mongo TokuMX mongo shell v2.0.0-mongodb-2.4.10 connecting to: test Mon Oct 6 20:36:54.462 Error: couldn't connect to server 127.0.0.1:27017 at /data/package-deb-ubuntu-precise/build/tokumx-2.0.0/src/mongo/shell/mongo.js:145 exception: connect failed

In: /var/logs/tokumx/tokumx.log I get nothing after the stopping of tokumx, in conclusion the service is not starting again, because of the FastUpdates parameter I added, if I remove it I am able to start tokumx again. Mon Oct 6 20:36:40.196 [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends Mon Oct 6 20:36:40.196 [signalProcessingThread] aborting any live transactions Mon Oct 6 20:36:40.196 [signalProcessingThread] now exiting Mon Oct 6 20:36:40.196 dbexit: Mon Oct 6 20:36:40.196 [signalProcessingThread] shutdown: going to close listening sockets... Mon Oct 6 20:36:40.197 [signalProcessingThread] closing listening socket: 16 Mon Oct 6 20:36:40.197 [signalProcessingThread] closing listening socket: 18 Mon Oct 6 20:36:40.197 [signalProcessingThread] closing listening socket: 21 Mon Oct 6 20:36:40.197 [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock Mon Oct 6 20:36:40.197 [signalProcessingThread] shutdown: going to flush diaglog... Mon Oct 6 20:36:40.197 [signalProcessingThread] shutdown: going to close sockets... Mon Oct 6 20:36:40.197 [signalProcessingThread] shutdown: going to close databases... Mon Oct 6 20:36:40.200 [signalProcessingThread] shutdown: going to unload all plugins... Mon Oct 6 20:36:40.200 [signalProcessingThread] shutdown: going to shutdown TokuMX... Mon Oct 6 20:36:40.200 [signalProcessingThread] [tokumx] shutdown Mon Oct 6 20:36:40.329 [signalProcessingThread] shutdown: removing fs lock... Mon Oct 6 20:36:40.329 dbexit: really exiting now

Maybe I am setting the parameter in the wrong file?

— Reply to this email directly or view it on GitHub.

alberto1el commented 9 years ago

Great! that was it Thank you very much @leifwalsh will use JIRA for future issues