meteor up - mup setup deploy error on digitalocean - meteor

Sorry for the question, but i didn't find any useful answer until now.
I am trying to follow a simple tutorial , and everything is going fine.
But when i type 'mup setup' on my local pc, I got this error:
Started TaskList: Setup Docker
[---.--.-.254] - Setup Docker
[---.--.-.254] x Setup Docker: FAILED
-----------------------------------STDERR-----------------------------------
bash: line 7: docker: command not found
rm: cannot remove ‘/var/cache/apt/archives/lock’: No such file or directory
W: Failed to fetch http://ubuntu.kurento.org/dists/xenial/InRelease Unable to find expected entry 'km6/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)
E: Some index files failed to download. They have been ignored, or old ones used instead.
-----------------------------------STDOUT-----------------------------------
ce.com wily/main Translation-en [162 B]
Get:7 https://deb.nodesource.com wily/main Translation-en_US [162 B]
Get:8 https://deb.nodesource.com wily/main Translation-en [162 B]
Get:9 https://deb.nodesource.com wily/main Translation-en_US [162 B]
Hit http://downloads-distro.mongodb.org dist/10gen amd64 Packages
Get:10 https://deb.nodesource.com wily/main Translation-en [162 B]
Get:11 https://deb.nodesource.com wily/main Translation-en_US [162 B]
Hit http://downloads-distro.mongodb.org dist/10gen i386 Packages
Get:12 https://deb.nodesource.com wily/main Translation-en [162 B]
Get:13 https://deb.nodesource.com wily/main Translation-en_US [162 B]
Ign https://deb.nodesource.com wily/main Translation-en_US
Get:14 https://deb.nodesource.com wily/main Translation-en [162 B]
Ign https://deb.nodesource.com wily/main Translation-en
Ign http://downloads-distro.mongodb.org dist/10gen Translation-en_US
Ign http://downloads-distro.mongodb.org dist/10gen Translation-en
Fetched 12.8 kB in 3s (4,015 B/s)
----------------------------------------------------------------------------
Note that login is succesful (I tried entering in mup.js a wrong password and process stops before all this).
Does anyone have an idea of why I'm getting this error and how to solve this? Do I have to install something on remote server?

Have you tried to run sudo apt-get -f install on a remote server?
In my case this command has solved the issue.

Related

mysql_grants.present fails to execute with salt-stack

I'm new with saltstack, state file that i'm using:
mybd:
mysql_database.present
user22:
mysql_grants.present:
- grant: ALL PRIVILEGES
- database: 'mybd.*'
- user: user22
- host: localhost
- connection_user: root
- connection_host: localhost
- connection_pass: ''
- connection_unix_socket: /tmp/mysql.sock
- connection_charset: utf8
I am getting the following error when applying a mysql state:
ID: mybd
Function: mysql_database.present
Result: True
Comment: Database mybd is already present
Started: 09:05:09.366441
Duration: 5.835 ms
Changes:
ID: user22
Function: mysql_grants.present
Result: False
Comment: Failed to execute: "GRANT ALL PRIVILEGES ON mybd.* TO user22#localhost"
Started: 09:05:09.372849
Duration: 76.012 ms
Changes:
Summary for user
Succeeded: 1
Failed: 1
but when I go to mysql i notice that the privilege is added !
I don't know what I am doing wrong. Is there somebody who knows how to properly grant permissions to a user in mysql through salt-stack?
Salt Version:
Salt Version:
Salt: 2015.8.0
Dependency Versions:
Jinja2: 2.7.2
M2Crypto: 0.31.0
Mako: Not Installed
PyYAML: 3.11
PyZMQ: 15.3.0
Python: 2.7.5 (default, Nov 16 2020, 22:23:17)
RAET: Not Installed
Tornado: 4.2.1
ZMQ: 4.1.4
cffi: Not Installed
cherrypy: Not Installed
dateutil: Not Installed
gitdb: Not Installed
gitpython: Not Installed
ioflo: Not Installed
libnacl: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.6.2
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: 2.6.1
pygit2: Not Installed
python-gnupg: Not Installed
smmap: Not Installed
timelib: Not Installed
System Versions:
dist: centos 7.9.2009 Core
machine: x86_64
release: 3.10.0-1160.15.2.el7.x86_64
system: CentOS Linux 7.9.2009 Core
mysql version:
mysql Ver 15.1 Distrib 10.3.31-MariaDB, for Linux (x86_64) using readline 5.1
To know the real answer you will have to look at the minions log file. If there are any errors listed that would be why the mysql.grant_add failed.
however the way the state works is it tries to determine if the grant is already there by using the mysql module to run mysql.grant_exists and look for the grant in the database. If it doesn't find it it will run the mysql.grant_add function.
mysql.grant_add will generate the query for the grant based on the information, run the query, if either of those processes fail it will report the failure in the minion log.
After that mysql.grant_add will run mysql.grant_exists to see if the grant was added. If that doesn't return properly it will report the failure. So the question is if mysql.grant_exists can see the grant.
Also with you being on such an old version of salt but a newer version of mysql it is possible that the grant table is not returning in a way that mysql.grant_exists can detect the grant. In which case it will detect as a failure and still be able to add.

brew install mariadb fails as system can not chown for auth_pam_tool

brew
brew install not work. this is the log.
% brew install mariadb
==> Downloading https://homebrew.bintray.com/bottles/mariadb-10.4.13.mojave.bottle.tar.gz
Already downloaded: /Users/shingo/Library/Caches/Homebrew/downloads/d56104142081a8230646ac3f245adf2414e515cd5f2aeeb0637614e9966e882c--mariadb-10.4.13.mojave.bottle.tar.gz
==> Pouring mariadb-10.4.13.mojave.bottle.tar.gz
==> /usr/local/Cellar/mariadb/10.4.13/bin/mysql_install_db --verbose --user=shingo --basedir=/usr/local/Cellar/mariadb/10.4.13 --datadir=/usr/local/var/mysql --tmpdir=/tmp
Last 15 lines from /Users/shingo/Library/Logs/Homebrew/mariadb/post_install.01.mysql_install_db:
shell> /usr/local/Cellar/mariadb/10.4.13/bin/mysql -u root mysql
mysql> show tables;
Try 'mysqld --help' if you have problems with paths. Using
--general-log gives you a log in /usr/local/var/mysql that may be helpful.
The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
You can find the latest source at https://downloads.mariadb.org and
the maria-discuss email list at https://launchpad.net/~maria-discuss
Please check all of the above before submitting a bug report
at http://mariadb.org/jira
Warning: The post-install step did not complete successfully
You can try again using `brew postinstall mariadb`
==> Caveats
A "/etc/my.cnf" from another install may interfere with a Homebrew-built
server starting up correctly.
MySQL is configured to only allow connections from localhost by default
To start mariadb:
brew services start mariadb
Or, if you don't want/need a background service you can just run:
mysql.server start
==> Summary
🍺 /usr/local/Cellar/mariadb/10.4.13: 744 files, 169.9MB
I have tried to execute mysql_install_db
I have tried to execute mysql_install_db without brew. this is the log.
The brew displays only the last 15 lines, so I can't help it.
% /usr/local/Cellar/mariadb/10.4.13/bin/mysql_install_db --verbose --user=shingo --basedir=/usr/local/Cellar/mariadb/10.4.13 --datadir=/usr/local/var/mysql --tmpdir=/tmp
chown: /usr/local/Cellar/mariadb/10.4.13/lib/plugin/auth_pam_tool_dir/auth_pam_tool: Operation not permitted
Couldn't set an owner to '/usr/local/Cellar/mariadb/10.4.13/lib/plugin/auth_pam_tool_dir/auth_pam_tool'.
It must be root, the PAM authentication plugin doesn't work otherwise..
Installing MariaDB/MySQL system tables in '/usr/local/var/mysql' ...
2020-05-29 22:13:03 0 [Note] /usr/local/Cellar/mariadb/10.4.13/bin/mysqld (mysqld 10.4.13-MariaDB) starting as process 45440 ...
2020-05-29 22:13:03 0 [ERROR] /usr/local/Cellar/mariadb/10.4.13/bin/mysqld: option '--innodb-large-prefix' requires an argument
2020-05-29 22:13:03 0 [ERROR] Parsing options for plugin 'InnoDB' failed.
2020-05-29 22:13:03 0 [ERROR] /usr/local/Cellar/mariadb/10.4.13/bin/mysqld: unknown variable 'mysqlx-bind-address=127.0.0.1'
2020-05-29 22:13:03 0 [ERROR] Aborting
Installation of system tables failed! Examine the logs in
/usr/local/var/mysql for more information.
The problem could be conflicting information in an external
my.cnf files. You can ignore these by doing:
shell> /usr/local/Cellar/mariadb/10.4.13/bin/mysql_install_db --defaults-file=~/.my.cnf
You can also try to start the mysqld daemon with:
shell> /usr/local/Cellar/mariadb/10.4.13/bin/mysqld --skip-grant-tables --general-log &
and use the command line tool /usr/local/Cellar/mariadb/10.4.13/bin/mysql
to connect to the mysql database and look at the grant tables:
shell> /usr/local/Cellar/mariadb/10.4.13/bin/mysql -u root mysql
mysql> show tables;
Try 'mysqld --help' if you have problems with paths. Using
--general-log gives you a log in /usr/local/var/mysql that may be helpful.
The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
You can find the latest source at https://downloads.mariadb.org and
the maria-discuss email list at https://launchpad.net/~maria-discuss
Please check all of the above before submitting a bug report
at http://mariadb.org/jira
I noticed that the system can not chown for auth_pam_tool because Operation not permitted.
auth_pam_tool permission
this is my permission the directory.
% ls -l /usr/local/Cellar/mariadb/10.4.13/lib/plugin/auth_pam_tool_dir/auth_pam_tool
-r-xr-xr-x 1 shingo staff 13608 5 10 04:28 /usr/local/Cellar/mariadb/10.4.13/lib/plugin/auth_pam_tool_dir/auth_pam_tool
How to fix Operation not permitted?
Or is there any other reason why it cannot be installed?
Self resolved.
Anyway I gave it try start
Even though the installation was not successful, anyway I gave it try % mysql.server start.
A error log file was created.
A error log file was created by starting mysql server.
the error log shows:
2020-05-30 8:47:10 0 [Warning] InnoDB: innodb_open_files 300 should not be greater than the open_files_limit 256
2020-05-30 8:47:10 0 [ERROR] /usr/local/Cellar/mariadb/10.4.13/bin/mysqld: unknown variable 'mysqlx-bind-address=127.0.0.1'
2020-05-30 8:47:10 0 [ERROR] Aborting
An unknown value in the mysqlx-bind-address seems to be causing the error.
How to fix unknown variable
I found
the same error question. This question discussed a my.conf file.
~/.my.conf did not exist on my mac
/etc/my.conf did not exist on my mac
this question teach me the my.conf location.
Finally I found my.conf in /usr/local/etc/my.cnf.Certainly the settings for mysqlx-bind-address were written in my.conf.
So rm /usr/local/etc/my.cnf, then brew reinstall SUCCESS!.
The permission was irrelevant at all.
this work for me:
rm /opt/homebrew/etc/my.cnf

Skipping acquire of configured file

I tried to update my raspberry pi 4 and I got this result.
$ sudo apt update
Hit:1 https://deb.nodesource.com/node_6.x xenial InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://repos.influxdata.com/debian buster InRelease
Get:4 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Hit:5 https://packages.grafana.com/oss/deb stable InRelease
Get:7 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]
Ign:6 https://download.rethinkdb.com/apt buster InRelease
Hit:8 https://download.rethinkdb.com/apt buster Release
Fetched 13.0 MB in 50s (263 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
N: Skipping acquire of configured file 'main/binary-armhf/Packages' as repository 'http://download.rethinkdb.com/apt buster InRelease' doesn't support architecture 'armhf'
$ lscpu
Architecture: armv7l
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Vendor ID: ARM
Model: 3
Model name: Cortex-A72
Stepping: r0p3
CPU max MHz: 1500.0000
CPU min MHz: 600.0000
BogoMIPS: 108.00
Flags: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
I am newbie in Linux. I spend my time a lot to figure out this problem and also i can not run node-red and Grafana I have no idea because of it.
To fix this,
Type the following commands:
sudo cd /etc/apt/sources.list.d
ls -a
Go into apt source folder and see what request/hits on the internet it is trying to make and list all the folders so you can identify the name of the folder you need to delete (rethinkdb folder/file)
sudo rm <folder/file that is causing the error, in this case, the rethinkdb>
clear
sudo apt-get update
Things should work now. The error was caused because the rethinkdb module you tried to download is not compatible with the architecture of your raspberry pi; so every time you try to update your pi it tries to download that file from the internet and the error happens.

Centos sudo yum update fails

I have the following error when trying to update yum for security can someone advise a fix, i have run yum clean metadata and that didnt work i am worried about running yum clean all as this was suggested as a fix in another post as i am not sure what it does?
sudo yum update
Loaded plugins: priorities, update-motd, upgrade-helper
amzn-main/latest | 2.1 kB 00:00
amzn-updates/latest | 2.3 kB 00:00
centos | 3.7 kB 00:00
http://apt.sw.be/redhat/el5/en/x86_64/dag/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
epel/x86_64/metalink | 23 kB 00:00
epel/x86_64 | 4.3 kB 00:00
epel/x86_64/updateinfo | 736 kB 00:00
epel/x86_64/primary_db | 5.9 MB 00:00
http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
rpmforge | 1.9 kB 00:00
4028 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package aws-cli.noarch 0:1.10.46-1.40.amzn1 will be updated
---> Package aws-cli.noarch 0:1.10.56-1.41.amzn1 will be an update
---> Package compat-libtiff3.x86_64 0:3.9.4-10.13.amzn1 will be updated
---> Package compat-libtiff3.x86_64 0:3.9.4-18.14.amzn1 will be an update
---> Package curl.x86_64 0:7.40.0-8.58.amzn1 will be updated
---> Package curl.x86_64 0:7.40.0-8.59.amzn1 will be an update
---> Package dracut.noarch 0:004-336.28.amzn1 will be updated
---> Package dracut.noarch 0:004-409.31.amzn1 will be an update
http://apt.sw.be/redhat/el5/en/x86_64/dag/repodata/filelists.sqlite.bz2: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
Thanks
You should delete invalid repo file in /etc/yum.repos.d/ directory.
First detect repo file with:
# grep -l apt.sw.be /etc/yum.repos.d/
Delete invalid repo file and clean yum cache with:
# sudo yum clean all
Although AliOkan provided a valid answer, here is the reason why it fails in the first place, as I've hit the similar issue as well.
As from your trace (you actually had a ref to el5 btw, which is not maintained anymore):
http://apt.sw.be/redhat/el[5|6]/en/x86_64/dag/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
This error points to some issue with RPMForge repo, then on the official repo there's this info:
RPMforge/RepoForge status
RPMForge/RepoForge is a dead project. It is not maintained. DO NOT
USE.
See also https://github.com/repoforge/rpms/issues/375
It's not officially maintained anymore, but if needed, there are mirrors in place, see git issue above.

Failed to bind to '127.0.0.1:6600': Address already in use

I'm using ubuntu 12.10 for my MPI(message passing interface) configuration I have installed mpd after installation I have start mpd, it is started normally no error message display but when I'm trying to run the command "mpd &" it gives me error message "Failed to bind to '127.0.0.1:6600': Address already in use" I have tried many solutions but the result is same.
root#ub0:~# service mpd start
Starting Music Player Daemon mpd
[ OK ] root#ub0:~# service mpd restart
Stopping Music Player Daemon mpd
[ OK ] Starting Music Player Daemon mpd
[ OK ] root#ub0:~# mpd &
[1] 2881 root#ub0:~# Failed to bind to '127.0.0.1:6600': Address
already in use
[1]+ Exit 1 mpd
root#ub0:~#
If you're using an old enough version of MPICH, the launcher is called MPD, which appears to conflict with something else you have installed on your system. I could try to help you with that, but the best answer is that you're using a very old version of MPICH and you should update. 3.1.1 came out yesterday. Give that a shot.

Resources