apt-key adv --keyserver subkeys.pgp.net --recv-key E58FE9B3FE3B0470525159BD6DC3D600CDEF74BB
apt-get install dirmngr
This issue may be caused by a buggy package installation script causing incorrect repositories to be added to the software sources repository list. If after troubleshooting the issue remains unresolved contact your vendors by opening a support ticket with the error details.
Other error message:
gpg: failed to start the dirmngr ‘/usr/bin/dirmngr’: No such file or directory
Working with Meteor templates one must understand how to access data context in the various sections of templates.
These links provide good explanations:
The defautl vm.swappiness value for Proxmox 5.2.x is 60
Run this command in Shell in order to reduce swappiness to an absolute necessity when the system is out of RAM.
sysctl -w vm.swappiness=0
Other performance tips
Proxmox OpenVZ SWAP and Performance
After adding a mongodb you may experience an error about the GPG PUB KEY like teh following.
W: GPG error: http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/testing Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 68818C72E52529D4
E: The repository ‘http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/testing Release’ is not signed.
You can fix this issue by adding the PUB KEY for MongoDB’s repository.
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68818C72E52529D4
Try update again
I don’t like to use big repeating command and I was searching for a solution where I will be setting a variable embedded with something so every time I start my meteor app; the MONGO_URL will set to environment automatically. So this what I did:
In the package.json file I replaced the start parameter as below:
"start": "MONGO_URL=mongodb://username:password@host_url:portnumber/dbname meteor run"
When trying to setup a meteor up node on proxmox CT the console will give out this error.
failed to register layer: ApplyLayer exit status 1 stdout: stderr: permission denied
This is because a container is being created within a container.
The soluton is to create a VM instead of a CT.
Another common error:
Error: Cannot find module ‘@babel/runtime/helpers/builtin/interopRequireDefault’
How to fix:
This has been traced in the forums as an incompatibility with the latest version of
@babel/runtime. Change the corresponding line in the package.json file
and then do
meteor npm install
Configure your instance using this guide to install the necessary packages and setup VNC to start on reboot.
Tip: You will want to connect via SSH tunnel to your VNC server. That is the safest way to do it.
Specify the resolution using this format
vncserver :1 -geometry 1600x1200
When you have issues with GitLab you will want to check the status to see which component of gitlab is not working as expected. Do this using the following command:
sudo gitlab-ctl status
Verify the log files of the component to obtain details about the failure. Log files for Omnibus installation of gitlab are located under.
Within this location there are several subfolders that container log files.
You will can to examine the file that is named current for the component.
Example, suppose we are fixing database is shutdown error.
sudo nano /var/log/gitlab/postgresql/current
When we examine this log file we discover there is an issue with reading the cacert.pem file. This is causing the database to be unable to startup.
FATAL: could not load root certificate file "/opt/gitlab/embedded/ssl/certs/cacert.pem": No such file or directory
LOG: database system is shut down
If the file is missing then you need to restore it from your backups.
If the file is there the error could be caused by a permission error.
Change the files permission using the commands below and restart gitlab.
sudo chmod 644 /opt/gitlab/embedded/ssl/certs/cacert.pem
sudo gitlab-ctl restart
Verify that gitlab is started correctly
sudo gitlab-ctl status
Windows, Linux (Ubuntu, Mint, Debian etc…), MacOS may be affected by this issue if you are using running a guest operating system and trying to use Discord.
In order to resolve this issue follow these simple steps.
- First shutdown your Virtualbox guest instance.
- Next go to select you Virtualbox and click the Settings icons in toolbar.
- Go to Display panel and uncheck ‘Enable 3D Acceleration’
- Click OK to save the settings
Now restart your Virtualbox guest instance and try startup Discord again.
Note: As this entry is being created the latest version of Discord is 0.0.5 for Linux.