I have a VPS (with OVH.com) running Vesta cp. I recently installed IonCube Loader (to run boxbilling) with success.
I believe it was because of this that my named services now fail to restart, however I cannot be sure. But ever since I installed IonCube Loader they have been functioning incorrectly.
The error I get is: zone [domain].com/IN: loading from master file /home/admin/conf/dns/[domain].db failed: file not found.
I get this with all of my domains I have currently registered with Vesta. Just in case you need it, I run the nameservers through cloudflare before they are forwarded to my VPS.
BoxBilling version 4+ does not require IonCube loader plugin.
You can download latest BoxBilling release from github
Update from 3.6 to 4 can be tricky.
Related
I installed SublimeText 3 (V 3207) on Windows today and Cannot get package installation working. It gave me errors in installing Package Control as well but looking at web I was able to clone the GIT repo to get it installed. But still the Install Package returns with 502 error.
Package Control: Error downloading channel. HTTP error 502 downloading https://packagecontrol.io/channel_v3.json
https://packagecontrol.io cannot be reached directly either. Is there an alternate way to download packages?
Package Control was down due to a migration being carried out by the author. Last year there was a failure on the machine that hosts the site and it was migrated to a backup machine, but the IP address changed and that IP address was one that is blocked in China.
The migration that was done last night moves the site to a new VM that uses the same IP address that it had back before that outage, which restores the ability of China to see and install packages.
The migration is now complete and everything should be working correctly. There is no official backup site, though.
I'm trying to set up a create-react-app project on my 918+ Synology NAS. From the getgo it has Node.js 5.6.0, but since create-react-app requires >=6 I need to install and use a higher version. Within the Synology NAS the Package Manger has both Node.js 6 and 8. These install fine. Then I'm trying to change the current Node.js version, this is where the problems starts.
For the information, the Synology runs a custom distro of Linux called DSM, with kernel 4.4.59.
When trying to change to version using e.g. nvm use 6.12.3 I get:
Error: Could not open history file.
REPL session history will not be persisted.
Googling this gives me no results. Is there somewhere here that would happen to know what to do, or just could try help me get this set up? I'm not sure if it's even possible. The Synology has Docker, would that be a better option for me?
I am not sure if it is the right place to ask this question. I have been trying to install clearcase client 8015 on a new machine with RHEL5u8 image. Tried googling a lot but could not resolve the issue as per suggestions on other forums.
It gets installed successfully. (As per the prompt)
listing of the views is done properly. (cleartool lsview)
When I do cleartool mount -all,
cleartool: Error: The MVFS file system is not installed or not loaded,
or the 'viewroot' is not mounted or is inaccessible: not a ClearCase
object.
logging in as root then starting clearcase, executing "/opt/rational/clearcase/etc/clearcase start"
OUTPUT:-
ClearCase is stopped Starting ClearCase ClearCase daemons: albd_server
FATAL: Error inserting mvfs
(/lib/modules/2.6.18-308.4.1.0.1.el5/kernel/fs/mvfs/mvfs.ko): Unknown
symbol in module, or unknown parameter (see dmesg) Loading the MVFS
was unsuccessful(8:1) /opt/rational/clearcase/etc/clearcase: Loading
MVFS failed
---- Please review /var/log/messages for information on the problem.
---- You may need to rebuild your kernel, rebuild your mvfs module,
---- and reboot your system. Information on how to do this can be found in
---- your Release Notes and file /var/adm/rational/clearcase/mvfs/mvfs_src/README.txt.
I have followed all the steps in /var/adm/rational/clearcase/mvfs/mvfs_src/README.txt but still cannot achieve anything.
Uninstallation also fails as:-
./linux_8015_uninstall
ERROR: Installation data has incompatible version 1.8.0; expected
1.7.0. Newer version of the Installation Manager was used on this system.
java.io.IOException: Installation data has incompatible version 1.8.0;
expected 1.7.0. Newer version of the Installation Manager was used on
this system.
00:01.33 ERROR [main]
com.ibm.cic.agent.core.application.HeadlessApplication run
Installation data has incompatible version 1.8.0; expected 1.7.0.
Newer version of the Installation Manager was used on this system.
java.io.IOException: Installation data has incompatible version 1.8.0;
expected 1.7.0. Newer version of the Installation Manager was used on
this system. java.io.IOException: Installation data has incompatible
version 1.8.0; expected 1.7.0. Newer version of the Installation
Manager was used on this system.
at com.ibm.cic.agent.internal.core.InstallRegistryParser.parse(InstallRegistryParser.java:160)
at com.ibm.cic.agent.internal.core.InstallRegistry.load(InstallRegistry.java:679)
at com.ibm.cic.agent.internal.core.InstallRegistry.openFile(InstallRegistry.java:485)
at com.ibm.cic.agent.internal.core.InstallRegistry.open(InstallRegistry.java:429)
Cannot proceed with installation, cannot uninstall either to try another version of clearcase, tried googling for the version mismatch of IBM installation manager but could not find anything addressing the issue properly for Linux.
Any suggestions on how to proceed? I am new to clearcase tool.
Usually, when I see only snapshot views are supported, and MVFS (for dynamic views) hasn't installed properly, I uninstall everything and try the all process from the start again.
In your case, that means installing or downgrading the IBM IM Installation Manager to the right version (similar to this issue).
It can be an IM update issue, as seen in this technote.
Further to #VonC's comment re: incompatible IM install,
review the following doc: MVFS not loading after kernel upgrade or is missing after installation on Linux.
I encountered a similar problem after an incompatible kernel path / ClearCase version. In my case, the error was similar to what is documented here in the post MVFS not installed - RHEL6 and I had to edit the kernel source to the same as the patch and rebuild. Then things stared up fine.
Review also the link How to manually restore a pre-built MVFS on Linux.
If the corresponding kerenl level is not provided it will not start and you will have to patch and make your own.
I have an RStudio server (0.99.441) instance shared by several users, running on an Ubuntu 12.04 server with R 3.2.0.
One user complained that the statement library(manipulate) was crashing because the package was missing. Looking into the issue, I found that some users had the manipulate package installed in their home under /home/user/R/x86_64-pc-linux-gnu-library/3.2/manipulate when others didn't. No trace of it in the system libraries. The users who do have it didn't install or copy it manually, so it was installed there automatically.
From what I have found, the manipulate package comes with the rstudio package, and with RStudio desktop they are installed automatically at session startup if not found. However this does not happen when starting a new session on RStudio server, and I couldn't find documentation on this issue.
One solution could be to simply copy these folders to the other users' homes, or even to the system library (rstudio package comes with RStudio and is not on CRAN), but I would like to understand how these packages ended up there in the first place and to find a clean way to install them.
I'm trying to install the Java Hosting Package distributed by Helicon Zoo in order to host a java project (.war file) on IIS. The problem I'm having is that I can't install the package because Jetty 8 can't be installed.
At first it complained about Jetty 7 aswell but after I downloaded it, that was removed. This didn't however work for Jetty 8.
Error message on web platform installer (Screenshot):
http://imgur.com/qUgH5dW
Has anyone seen this before and possibly fixed it?
Hmm, It seems as if the url that the package is trying to fetch Jetty from: dist.codehaus.org/jetty/jetty-hightide-8.1.7/… has been shut down. I removed Jetty8 (which I manually installed to try to fix the issue, and downloaded it again from download.eclipse.org/jetty. This seems to have fixed the issue. Don't know what the issue was with the first download but maybe it was corrupt.