I am new to Plone and Solaris - I'm attempting to install Plone 5 on Solaris 11. Seems to be hanging up on the Zope install. Here is the install.log:
Detailed installation log
Starting at Wed Oct 14 11:41:13 AKDT 2015
The directory '/home/dotasdis/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/home/dotasdis/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Processing ./packages/zc.buildout-2.4.3.tar.gz
Requirement already satisfied (use --upgrade to upgrade): setuptools>=8.0 in /opt/plone/zinstance/lib/python2.7/site-packages (from zc.buildout==2.4.3)
Installing collected packages: zc.buildout
Running setup.py install for zc.buildout
Successfully installed zc.buildout-2.4.3
/opt/plone/zinstance/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
InsecurePlatformWarning
Creating directory '/opt/plone/zinstance/parts'.
Creating directory '/opt/plone/zinstance/develop-eggs'.
Not found: /opt/plone/buildout-cache/downloads/dist/ZODB3/
Not found: /opt/plone/buildout-cache/downloads/dist/ZODB3/
Getting distribution for 'ZODB3==3.10.5'.
gcc: cg: No such file or directory
gcc: unrecognized option '-Qoption'
gcc: unrecognized option '-KPIC'
gcc: language O5 not recognized
gcc: language O5 not recognized
error: Setup script exited with error: command '/usr/gcc/4.5/bin/gcc' failed with exit status 1
An error occurred when trying to install ZODB3 3.10.5. Look above this message for any errors that were output by easy_install.
While:
Installing.
Getting section instance.
Initializing section instance.
Installing recipe plone.recipe.zope2instance.
Getting distribution for 'ZODB3==3.10.5'.
Error: Couldn't install: ZODB3 3.10.5
Any help is greatly appreciated.
Related
I'm running Vagrant version 2.2.19 with VirtualBox version 6.1 on Mac OS Monterey version 12.3.1.
When running vagrant up or vagrant up --provision, I'm receiving the following error:
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Upon checking the logs, in provisioner-utility-source-core.log I can see the following log:
[0;38;5;2m ▷ Running the [0m[1m[0;38;5;5m'utility-source-core'[21m[0;38;5;2m provisioner...[0m[0m[0m
[0m[39m[2m* Updating the "core" utility on the "master" branch...[21m[0m
fatal: unsafe repository ('/srv/provision/utilities/core' is owned by someone else)
To add an exception for this directory, call:
git config --global --add safe.directory /srv/provision/utilities/core
[0;38;5;9m ! The [0m[1m[0;38;5;5m'utility-source-core'[21m[0;38;5;9m provisioner ran into problems, the full log is available at [0m[1m[0;38;5;5m'/var/log/provisioners/2022.04.18_18-32-31/provisioner-utility-source-core.log'[21m[0;38;5;9m. It completed in [0m[1m[0;38;5;5m0[21m[0;38;5;9m seconds.[0m[0m
In the above, can see a fatal error:
unsafe repository ('/srv/provision/utilities/core' is owned by someone else)
However, I cannot see any resources online to solve the above fatal error.
What I've tried:
Running vagrant halt then vagrant destroy and then vagrant up to create the box again, and then running vagrant up to see if it solves things (get the same error)
Added Git SSH (using this guide) in case it was a Git error
Uninstalled and then reinstalled VirtualBox
Cleared out IPs from /etc/hosts/hosts, and then ran vagrant up again, to see if there were any conflicts.
Have tried running git config --global --add safe.directory /srv/provision/utilities/core, then re-ran vagrant up --provision - but it does nothing.
Note: I have allowed oracle permissions via security and privacy and have rebooted my machine so it's in effect.
Is there any way to get VVV running again?
This is a known issue that was fixed in newer versions of VVV. Update to at least VVV 3.10.1 and re-provision.
If it is still happening despite updating to newer VVV, raise a GitHub issue.
I'm the VVV project lead, usually when we see these issues we fix them, this isn't something you should need to fix yourself. But if you use stackoverflow to report bugs we don't see it. Either raise a GitHub issue or ask in the VVV slack.
https://github.com/Varying-Vagrant-Vagrants/VVV/issues/new/choose
I wanted to try learn things in DPDK in Debian 10 buster VM.
I have taken DPDK 20.08 as source.
I followed steps as mentioned in Compiling the DPDK Target from Source https://doc.dpdk.org/guides/linux_gsg/build_dpdk.html#uncompress-dpdk-and-browse-sources
I have tried to follow the below steps
tar xJf dpdk-<version>.tar.xz
cd dpdk-<version>
meson build
cd build
ninja
ninja install
ldconfig
On the above when I tried
ninja
it works. Then I went for next command
If I try with
sudo ninja install
from dpdk build directory
it says sudo: ninja: command not found
If I try
ninja install with out sudo
it gets terminated with error.
It asks for sudo password then shows
ModuleNotFoundError: No module named mesonbuild
Failed Meson-install
ninja:build stopped:subcommand failed
Would appreciate your help to resolve this step.
Edit
Repeated steps with root account. Problem didn't occur. Initially it was looking in /home/vijay/.local/bin folder. Then I used from /usr/local/bin/meson
The error information ninja: command not found could be 1 of the 2 things
either NINJA utility is not installed
or PATH for NINJA Binary is incorrect
As recommended in the comment, ensure 'ninja' is installed and you have the right path like /usr/bin/ for the same.
[EDIT] #Vijay has updated it is indeed the path related issue.
I'm getting this error when I try typing $modulus deploy into terminal from my app directory:
Determining Meteor version...
Meteor version: 1.1.0.2
Bundling Meteor App...
undefined
[Error] Error: Command failed: /bin/sh -c cd /Users/xx/Projects/Project1 && meteor bundle --directory /Users/xx/Projects/Project1/.demeteorized
This command has been deprecated in favor of 'meteor build', which allows you
to build for multiple platforms and outputs a directory instead of a single
tarball. See 'meteor help build'for more information.
WARNING: The output directory is under your source tree.
Errors prevented bundling:
While building the application:
client/Project1.js:138:29: Unexpected token =
I get the same result with $demeteorizer. It worked on an old version of the app, then I added some features in new branch, merged, and now I'm getting this error.
Already tried:
sudo npm update -g modulus
Turns out it was an actual error in my code. I had an extra closing curly brace somewhere.
A fresh plone install is failing with this error:
Copying buildout skeleton
Fixing up bin/buildout
Building Zope/Plone; this takes a while...
Buildout returned an error code: 126; Aborting.
Buildout failed. Unable to continue
Installation has failed.
See the detailed installation log at /home/adrigen/Downloads/Plone-4.3.2-UnifiedInstaller/install.log
The log says
/bin/sh: 1: /home/adrigen/Develop/Plone-4.3.2/zinstance/bin/buildout: Permission denied
The folder permissions say
drwxr-sr-x 7 plone_buildout plone_group 4096 Nov 21 19:01 Plone-4.3.2
This is when I run the install with and without a sudo prefix. What might the issue be here?
when i do this:
$ mrt create myapp
$ cd myapp
$ mrt
i get this error message:
livedata: updating npm dependencies -- sockjs, websocket...
No dependency info in bundle. Filesystem monitoring disabled.
=> Errors prevented startup:
Exception while bundling application:
Error: Command failed: npm WARN package.json packages-for-meteor-smartpackage-livedata#0.0.0 No README.md file found!
i have this from the new "discover meteor" book by sasha greif.
thanks in advance.
I had a similar problem as I was following through the Discover Meteor book as well. It might be the same error you are having but I can't remember it exactly, it was rather long and suggested running mrt as root/administrator. Also, I'm not sure if the error I was having was related to the version of Node.js that I was using (0.10.6 on Ubuntu).
Thanks to a comment posted on github by Apendua (https://github.com/apendua) I was able to run mrt successfully without having to run as root/administrator.
Here is what he found:
"What I've seen so far is the follwing. After calling:
sudo npm install -g meteorite
there is a mysterious tmp dir in my home with content owned by root. I don't think it's distribution specific since I've experienced this on Ubuntu 12.10 as well as on Ubuntu 13.04. Also, the content of .npm dir in my home is sometimes - but sometimes it is not - owned by root. Getting rid of tmp and changing privilages on .npm solevd the issue for me. No need to sudo mrt any more."