i am installing the influxdb_2.0.9 on my ubuntu, i followed the instructions here:
https://docs.influxdata.com/influxdb/v2.0/install/?t=Linux
I download it, setup it, i start the influxd daemon, i can connect via browser on localhost:8086, i think i can work with it, its functioning, i am gonna use the python API anyway, but this really drives me crazy...
I can't get to CLI. When i copy it to /usr/local/bin, or anywhere, or when i run it right in the directory via ./influx, it just returns a HELP message, like if i would type ./influx -h
Funny thing is when i download influxdb-client and run its influx binary, it starts the CLI, but its meant on version 1.6.4 and it does not seem to connect ideally on localhost running influxd 2.0.9, mbe i could somehow config it, but it seems to be bad idea anyway.
I purged everything, tried to reinstall everything, even manually deleted all empty directories, anything named influx on my 20.04 Ubuntu is gone and when i try to just follow the instructions online, everything seems to work except the CLI which i really **** need.
Just FYI, if i try to isntall via sudo apt-get install influxdb, influxdb-client -> it works perfectly, but it is older version 1.6.4
I tried installing the deb package via dpkg as well, but no difference... Im running 20.04 Ubuntu. There is the option of running older influxdb(1.6.x), but that I really dont want to do.
Anyone had the same problem? Could not find the solution in last hour online so im trying here to find help. This really drives me crazy though... Thanks for your time. Q.
Thank you guys for your time.
Well, i seem to realize, that the old CLI is gone and not implemented as it used to be, in the new version. In 2.0.0 it was started by
influx repl
But now i found a msg
I have no idea why they decided to deprecate this, not posting that much info about it..
I will try to finish this post by myself, leave it here, maybe someone in the future will find this useful.
Now I will try to 'build the REPL from source', wish me luck lol.
--EDIT
found a clone, closing the thread.
https://github.com/influxdata/influxdb/issues/19986
Related
Yeah, I know, there are some questions similar to that, but none of them helped me. My docker for windows has once stopped working. Now I can't even uninstall it, because in the applications it doesn't appear, I cannot install it, the installation stucks always on the same process, I tried to delete all the files and then install again, tried to stop all the proccesses related to docker, I tried everything. I cannot even uninstall, cannot reinstall, cannot run... cannot do anything with it... help!
I finally solved that. I deleted manually all the directories related to docker (ProgramFiles, ProgramData, [user root directory], Appdata/Roaming etc.) and this way the installer finally finished. There was another problem, that WSL2 engine tried to start, but couldn't. WSL was enabled, the engine starting process was running for ca. 1 hour... but nothing happend and couldn't even change the engine. So I reinstalled once again, and didn't install the WSL frame. It started automatically with Hyper-V and now it works fine.
We're working with GitLab 8.16.4 and I want to upgrade it but since the backups are not compatible between versions I want to make sure everything is ok first.
I've been trying to follow the recovery process in a VM (VirtualBox) and in a few Dockers and is not giving any error but not working either (opened an issue there too )
I don't know what to check, what I'm doing wrong or if I need to do anything specific on the GitLab server (backup job> gitlab-rake gitlab:backup:create SKIP=db,uploads )
Any ideas?
Note regarding the VM: This was created in the past to have a backup of GitLab and it did do the restore months ago, not sure what's going on now
Edit days later: Installed the whole thing on a physical server with Ubuntu 16.04, still doesn't work. What am I doing wrong?
Managed to make it work!!
Looks like the problem was on the way I was making the backup.
After doing it with:
gitlab-rake gitlab:backup:create RAILS_ENV=production
The restore worked fine with:
gitlab-rake gitlab:backup:restore BACKUP=<filename>
yesterday I just installed docker to my win 7 using docker toolbox... i refereed to some installation tutorials and successfully did it.. but now when I start docker terminal I'm getting following error.. I went through the websites but I'm unable to find solution,i have gone through many website for this question, they are teaching how to install it which I have done with same procedure Have I done any mistake in setting up of docker..??
can anyone guide me for the same.. I'm new to docker... thank you in advance
if your installing with boot2docker place the boot2doker.iso in cache i.e c:/username/.docker/machine/cache and re-run in terminal
This morning I've started playing with Docker, so installed boot2docker on my Mac.
All seemed to be going well, following the Working with Docker Images documentation until I tried to create a Dockerfile to install the ruby gems.
I spent a long time banging my head against the wall as to why it couldn't connect to install the gems... then I eventually worked it out, so adding this here in case anyone else has this problem in future, as there wasn't anything on Google about it.
Turns out that, because my internet bombed out during the apt-get update command, it didn't complete the update, however running it again, docker was using the cached (incomplete) data, and so if didn't work.
The fix... Run the docker build without the cache using the command...
docker build -no-cache --tag="<vendor>/<build>:<tag>" .
So, I thought I'd create a bonafide release to run my next application in. Unfortunately, there seems to be a deal breaker.
First I tried making a project from scratch using this guide:
http://alancastro.org/2010/05/01/erlang-application-management-with-rebar.html
That failed with an obscure error, so just to make sure, I tried to run a project I know is good, etorrent.
When I tried to run etorrent's release, I got the same error:
[me#my-ip etorrent]# rel/etorrent/bin/etorrent console
Exec: /root/etorrent/rel/etorrent/erts-5.8.4/bin/erlexec -boot /root/etorrent/rel/etorrent/releases/1.2.1/etorrent -embedded -config /root/etorrent/rel/etorrent/etc/app.config -args_file /root/etorrent/rel/etorrent/etc/vm.args -- console
Root: /root/etorrent/rel/etorrent
pthread/ethr_event.c:98: Fatal error in wait__(): Function not implemented (38)
Aborted
I searched for that error, and the serps are filled with references to RabbitMQ on CentOS having the same problem. Obviously, it's more general than a RabbitMQ problem specifically. Based on this thread:
RabbitMQ install issue on Centos 5.5
...and my own experience, it seems like running releases on 14 series erlang installations coupled with series 5 CentOS doesn't work. I installed the latest erlang up on the site last night, by the way, so that's what I'm using. I didn't pass any flags to 'configure', just used the stock options.
Does anyone have any idea if there's a compile option for erlang that might fix this? Or any other advice? Is anyone else successfully using rebar created releases for applications in this environment?
Seems to be a problem that needed to be solved on the CentOS side if you look at this comment to this RabbitMQ install issue on Centos 5.5 answer
Compilation of Erlang R14B03 (erts-5.8.4) works on CentOS 5.6 (Final)
VirtualBox VM
So it looks to me that you need to upgrade your CentOS to 5.6