Openstack installation issue on ubuntu-18.04 - ubuntu-18.04

$ cat /etc/issue
Ubuntu 18.04.6 LTS \n \l
I'm following this Link to install Openstack using Devstack. However git clone https://git.openstack.org/openstack-dev/devstack master branch's ./stack.sh fails with below error.
+./stack.sh:main:230 SUPPORTED_DISTROS='bullseye|focal|f34|opensuse-15.2|opensuse-tumbleweed|rhel8|rhel9|openEuler-20.03'
+./stack.sh:main:232 [[ ! bionic =~ bullseye|focal|f34|opensuse-15.2|opensuse-tumbleweed|rhel8|rhel9|openEuler-20.03 ]]
WARNING: this script has not been tested on bionic
+./stack.sh:main:234 [[ '' != \y\e\s ]]
+./stack.sh:main:235 die 235 'If you wish to run this script anyway run with FORCE=yes'
+functions-common:die:253 local exitcode=0
+functions-common:die:254 set +o xtrace
[Call Trace]
./stack.sh:235:die
[ERROR] ./stack.sh:235 If you wish to run this script anyway run with FORCE=yes
/opt/stack/devstack/functions-common: line 299: /opt/stack/logs/error.log: No such file or directory
Even ./stack.sh FORCE=yes and stable/newton, stable/pike, stable/victoria & stable/xena branch also results the same above error.
Does the support for Ubuntu 18.04.6 LTS (bionic) deprecated?

Does the support for Ubuntu 18.04.6 LTS (bionic) deprecated?
Not exactly.
As a general rule, the latest version of the script targets the latest supported (by Openstack) versions of the host operating systems. Older versions may work. But there might be minor issues ... that someone with the ability to read / diagnose shell scripts ought to be able to figure out.
If you need a version of the script that explicitly supports (say) Bionic, there will be one in the Git6 repo history.
(This is in line with general OpenStack Ubuntu support. The latest OpenStack release is Wallably and Wallaby no longer supports Bionic. The Bionic -> Focal cross-over release of Openstack was Ussuri; see https://ubuntu.com/openstack/docs/supported-versions. Note that Devstack is not an official OpenStack product, but they are effectively forced to track the "supported release" rules, at least loosely.)
The version of the Devstack script that you checked out does not explicitly supports Focal rather than Bionic.
If you look at https://opendev.org/openstack/devstack/src/branch/master/stack.sh on line 230, it currently says:
# Warn users who aren't on an explicitly supported distro, but allow them to
# override check and attempt installation with ``FORCE=yes ./stack``
SUPPORTED_DISTROS="bullseye|focal|f34|opensuse-15.2|opensuse-tumbleweed|rhel8|rhel9|openEuler-20.03"
If you want a version of devstack that explicitly supports bionic, use git blame (or whatever) to track changes to the SUPPORTED_DISTROS line. You should be able to find some versions where FORCE is not necessary.
On the other hand .... the error message:
/opt/stack/devstack/functions-common: line 299: /opt/stack/logs/error.log:
No such file or directory
implies that the script is assuming that a file or directory already exists. You could probably just create it / them by hand. (It is clearly just a log file / directory.)

Related

MariaDB version 10.5.9 unable to install

In my current workplace we are using MariaDB version 10.5.9 for our DB's and we are trying to reinstall this version for testing purposes on a separate container. However, seems anything from 10.5.9 below is failing with the follow error;
root#mdb-10-5:~# curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --mariadb-server-version=mariadb-10.5.9
# [info] Checking for script prerequisites.
# [warning] Found existing file at /etc/apt/sources.list.d/mariadb.list. Moving to /etc/apt/sources.list.d/mariadb.list.old_5
# [error] MariaDB Server version 10.5.9 is not working.
# Please verify that the version is correct.
#
# The latest MariaDB Server versions are:
# 10.10.1 10.3.36 10.4.26 10.5.17 10.6.10 10.7.6 10.8.5 10.9.3
#
# More information on MariaDB releases is available at:
# https://mariadb.com/kb/en/release-notes/
When I try the same command with version 10.5.10, it works and downloads successfully.
I am using the following procedure, one of which is the MariaDB KB:
https://mariadb.com/kb/en/mariadb-package-repository-setup-and-usage/
https://www.dbi-services.com/blog/how-to-install-a-specific-version-of-mariadb/
Both guides use the same repo, and it is also the only thing that I have found specific when I search for information to install this particular version or MariaDB.
Can anyone offer any suggestions or have experienced similar problems?
We (MariaDB corporation) recently moved over our repositories to a content delivery network instead of using our own servers only. Unfortunately the new service does not have a full archive of older releases yet, the oldest 10.5 we have on there for example is 10.5.10.
I have filed an internal bug report / feature request about that already, but it is still pending.
Meanwhile you can "fix" this by first running the repo setup script with a supported version like 10.5.10, and then editing the repository file it created, replacing the version number with 10.5.9, and the host name dlm.mariadb.com with download.mariadb.com.
On Debian and Ubuntu the repository file would be /etc/apt/sources.list.d/mariadb.list, and you'd have to run apt-get update afterwards to pick up the repo change before installing packages.
On RHEL, CentOS, Rocky etc. the file is /etc/yum.repos.d/mariadb.repo and no further action is needed before installing actual packages.

VOLTTRON install on rasbian buster

Can I get a tip for installing on rasp buster? Im hung up on the install directions to check the status of the rabbitMQ server. Traceback of bash console:
(volttron) pi#raspberry:~/Desktop/volttron $ echo 'export RABBITMQ_HOME=$HOME/rabbitmq_server/rabbitmq_server-3.7.7'|sudo tee --append ~/.bashrc
export RABBITMQ_HOME=$HOME/rabbitmq_server/rabbitmq_server-3.7.7
(volttron) pi#raspberry:~/Desktop/volttron $ source ~/.bashrc
pi#raspberry:~/Desktop/volttron $ RABBITMQ_HOME/sbin/rabbitmqctl status
bash: RABBITMQ_HOME/sbin/rabbitmqctl: No such file or directory
There are a few tracebacks earlier on the installation...
If it makes a difference or not here is the entire bash console process. The git gist link I just created the name install.py even though its just bash commands copied pasted per install directions...
`pi#raspberry:~/Desktop $ git clone https://github.com/VOLTTRON/volttron --branch releases/7.x`
It looks like there are a couple of different issues going on here:
The issue you quote above (RABBITMQ_HOME/sbin/rabbitmqctl: No such file or directory) is that your shell isn't finding the rabbitmqctl command. It looks like you added the RABBITMQ_HOME environment variable to your .bashrc, but used the string RABBITMQ_HOME instead of the variable expansion $RABBITMQ_HOME when you tried to run the command. Try running it as $RABBITMQ_HOME/sbin/rabbitmqctl status instead.
The rabbitmqctl status command will check the status of the rabbitmq application, but I don't think you've done anything to start it yet (that happens when you bootstrap the platform and/or start the platform configured to use the RMQ broker)
I think that the traces earlier in the installation process are problematic (appears to be the same error hit two different ways), but you just haven't run into them yet. I haven't seen any issues building gevent on the RPi 4 with buster (though it is pretty slow), but the ctypes error makes me wonder if there's an issue with the underlying c library it is trying to build on top of. I did notice that you're getting amd64 erlang packages, are you running Raspbian on an x86 processor? (if so this isn't a permutation we've tried and you may be hitting some package compatibility edge case we haven't seen)
One thing to try is to manually install cython into your virtualenvironment and then try running the bootstrap script again with the virtualenvironment activated. You could also try and pip install gevent==20.6.1 directly in that virtualenvironment (this is what the bootstrap script was doing at the failure point). VOLTTRON depends on gevent, so if that isn't installing the platform won't be able to run.

How to fix 'postgres.h' file not found problem?

I am trying to write a base type for PostgreSQL in C (using xcode), and I already installed PostgreSQL 11, but it seems that postgres.h cannot be simply included in the file ("'postgres.h' file not found").
Could someone tell me how to fix that problem? And can I write code under an arbitary directory, or do I have to write under the PostgreSQL directory?
Or perhaps the question should be: how to install header files like postgres.h?
Install postgresql-server-dev package with this command:
sudo apt install postgresql-server-dev-XX
Replace [XX] with your already installed version of postgresql:9.5, 10, 11, 12
You have several approaches here:
Search for the file yourself, using some command like
find / -name "postgres.h" -print
this will tell you (on my Mac does) the file is in:
/usr/local/Cellar/postgresql/11.2_1/include/server/postgres.h
and add the -I /usr/local/Cellar/postgresql/11.2_1/include/server option to the compiler. Check your postgresql version for the possibility of having a different one.
Probably there's another package for database development. Search for a package named postgresql-dev or similar, and install it. After searching packages with:
brew search postgres
and
brew search psql
on my system doesn't appear anything that matches.
EDIT
I've checked a FreeBSD system for that file and it appears on
/usr/local/include/postgresql/server/postgres.h
So probably you have to #include <server/postgres.h> instead, and use the appropiate -I flag (as mentioned above)
I was facing the same issue while compiling postgis 3.1.7 for postgresql#13 on my Mac.
The problem was that in pg_config the link to server file was
/opt/homebrew/opt/postgresql#13/include/server
While the actual server folder was in
/opt/homebrew/opt/postgresql#13/include/postgresql/server
So I moved the entire "server" folder up a directory inside "/include". And viola, postgis compiled and installed perfectly.

MacPorts: install hangs/remains unusable

I've been trying to install MacPorts on a new Mac Pro with a fresh, fully updated Yosemite OS. The installer hangs on 'Running package scripts'. So I tried to build it from source. That works, with the installer stating:
Congratulations, you have successfully installed the MacPorts system.
However, it seems unusable. When I do sudo port install apache2 I get the message:
Error: Port apache2 not found
Simply trying to do a 'self update' (as root):
sh-3.2# port -d selfupdate
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
---> Updating MacPorts base sources using rsync
receiving file list ... done
base.tar
...and then nothing... I've waited for half an hour, but it won't go any further. I can't find any logs either.
Again: there's nothing special about my setup, it's out-of-the-box Yosemite, only updated through the App store and, of course, I've installed Xcode with command line utilities and formally accepted the license, as is required according to the MacPorts site.
I've also tried uninstalling it, using the instructions from the MacPorts site, and reinstalling. But it does not make a difference.
I've read quite a few forum posts, but I can't find any post relating a problem like this. I hope someone can shed some light on this.
The installer hangs running package scripts because the last statement in these package scripts is exactly this "sudo port selfupdate" that you've been running manually afterwards.
Because this step did never run, your MacPorts installation lacks knowledge about the apache2 port (which is exactly why the installer runs selfupdate to give you a full-featured installation).
Unfortunately Apple's infrastructure (rsync.macports.org) seems to have connectivity problems at the moment, which is causing problems for quite a few people. You can try using one of the mirrors as outlined at https://trac.macports.org/wiki/Mirrors.

Not able build apache mod_tile in openSuse error: Could not find apxs on the path

I want to run a tiles server with OSM data
i want to install mod_tile so i followed the mod_tile setup
But when i do the
./configure
It says
checking for getloadavg... yes
checking for apxs... no
checking for apxs2... no
checking for /opt/local/apache2/bin/apxs... no
configure: error: Could not find apxs on the path.
any idea what went wrong?
According to the Internets you need to install apache2-dev (previously known as apache2-devel). The apx binary should then be located under /usr/bin/apxs2 or /usr/sbin/apxs2.
Note: For building a tile server you should follow the guide on switch2osm.
For Ubuntu
sudo apt-get install apache2-devel
For RedHat & CentOs
yum install httpd-devel
SUSE has removed the SDK ISO from the area where you download the server ISO.
Check out this page.
I consider their page as very complicated and not logical so play a bit around but you find it in the end.
When you are looking for a current version then it helps you check Last 6 months

Resources