Hello everyone I would like some help on the installation of openproject; I tell you right away that I have tried them all and the result is always the same when I try to access from the browser with http: // ip address the error message is always the following:
"" "" Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache / 2.4.41 (Ubuntu) Server at 54.172.171.10 Port 80 "" ""
I wonder I performed the installation as per the procedure from the official website. Here guide https://www.openproject.org/docs/installation-and-operations/installation/packaged/#ubuntu-2004
Not happy, I also decided to follow some videos on youtube and magically both the installation and the browser access succeed. Here video https://www.youtube.com/results?search_query=how+install+and+configure+openproject
I also state that I have enabled all ports both inbound and outbound
Also I am wondering, if the installation includes apache and postgresql installed during the openproject installation process, why am I getting apache not available error? Finally, I add that no error occurred during the installation and the linux distribution was virgin as soon as it was installed and updated from all the repositories with all the dependencies necessary for the installation of openproject
Hope someone can help me solve
Related
I have installed GitLabv13 on ubuntu 20.04 using the standard procedure where external_url is set to a relative URL, i.e., http://www.example.com/gitlab.
I get a 404 when I navigate to the URL via the web browser.
I tried the basic troubleshooting found on GitLab's site, but that does fix the problem.
I am not running any firewall, and port 80 is not blocked.
What else should I try?
First, the CPU/Memory requirements for GitLab are more than 1 CPU/2GB.
Second, make sure all configuration files listed in "Install GitLab under a relative URL" are modified.
The troubleshooting page suggests checking the format in gitlab.rb.
And issue 244 suggests, for testing, to force the IP address in /etc/hosts.
My solution was to shutdown the existing Apache webserver running on the same machine, at which point, I no longer received a 404. However, due to the minimum requirements - I am only running a single core CPU with 2GB RAM - I now receive a 502.
I'm trying to connect my computer to a local redhawk domain. After running omniorb4-nameserver and omniorb-eventservice services I enter the IDE and go to "launch domain" option. Then the domain manager starts successfully, but I can't connect to it. The following message appears:
Failed to connect to Domain REDHAWK_DEV
org.eclipse.core.runtime.CoreException: Error while executing callable. Caused by org.omg.CORBA.ORBPackage.InvalidName
I've already tried to erase the log files in /var/lib/omniorb and /var/lib/omniEvents, stop and start the omniorb4-nameserver abd omniorb-eventservice event services. Nothing worked. My /etc/omniORB.cfg follows the instructions in https://redhawksdr.github.io/Documentation/mainch2.html#x4-160002.3.
A similar question was proposed in REDHAWK_DEV FAILED on 2.0.0, CentOS 6.7, without any useful answer so far.
Any help is appreciated
Thanks
Check that "nameclt resolve REDHAWK_DEV/REDHAWK_DEV" results in an IOR, and that "catior IOR:XXXXX" shows an okay IP address for that IOR. This will at least determine if the domain manager is actually registering in the naming service.
Also take a look through Appendix H of the REDHAWK Manual for other troubleshooting steps.
It turns out my proxy server was blocking even local connections.
To solve the problem I had to edit /etc/environment, adding the line
no_proxy="127.0.0.1,127.0.1.1", which were the local IP's I was using, and reboot.
I was trying to install openstack using Mirantis. I successfully installed and configured Mirantis. I created 2 nodes and when I click "deploy" option it started deploying. When it is nearing to 100%, am getting this error in Astute logs.
Node 1(ntp-check) status: error puppet
Someone please help to fix this.
Finally, I fixed this issue. As my machine running behind office firewall. So, I couldn't access the ntp server URLs. After, the admin team provided access to those URLs and it is fixed.
On Linux (Gentoo) if I start GlassFish from Netbeans/Services area, the server will started, the admin site is reachable, but in Netbeans I get the following error message:
GlassFish Server 4.1 start failed.
Please check server admin user name and password properties.
Also please check the server log file for other possible causes.
and I can neither start again, nor terminate.
Any idea?
Well, I had the same situation but on Mac. After I updated to macOS Sierra. In my case was a block on the sites that use system proxy settings, where localhost, 127.0.0.1, are blocked.
Perhaps, your case es similar, but a proxy setting on you Linux (GENTO).
For mac this is the solution AppServer issues from Netbeans
Step 1: (Try to search for the same on Linux) Go to system preference >Network>Select your wifi connection>Advanced>select
proxies tab. There check 3 options 1) Auto proxy Discovery 2)Automatic
Proxy configuration 3) web proxy(http)
Step 2: Go to Netbeans>preferences>General> select use system proxy> reload> test connection You may get connection successful. If
connection gets successful, Now Clean & build your Applications in
netbeans and press run .
I hope this help you and give you an idea.
My coworker installed Linux Mint 14 Nadia onto a VM (using VirtualBox) and followed the following tutorial to install Apache, MySQL and PHP: http://community.linuxmint.com/tutorial/view/486. He then used the readme from http://www.bestpractical.com/rt/docs/4.0/ to install Request Tracker 4.0. Both of those went pretty well with very few hiccups along the way from what he told me. Now he's forwarded over the task to me and I'm attempting to get Request Tracker 4.0 configured correctly with the Apache server. Currently I can visit localhost and get the following message:
It works! This is the default web page for this server. The web server
software is running but no content has been added, yet.
I also configured it so when you visit localhost/rt you SHOULD see the Request Tracker interface, but I'm instead receiving the following page, and this is where I've spent most of my time stumped:
You're almost there! You haven't yet configured your webserver to run
RT. You appear to have installed RT's web interface correctly, but
haven't yet configured your web server to "run" the RT server which
powers the web interface. The next step is to edit your webserver's
configuration file to instruct it to use RT's mod_perl or FastCGI
handler. If you need commercial support, please contact us at
sales#bestpractical.com.
After a few moments it redirects me to bestpractical.com/rt/rt-broken-install.html. (only allowed 2 links apparently?)
I assume I have something misconfigured but am unsure what. I've been googling and fiddling around with this most of yesterday and today with no luck. It doesn't help that I'm fairly inexperienced with the linux environment, I'm sure.
If I understand how he installed it, he wants to set it up using FastCGI so I visited this site requesttracker.wikia.com/wiki/FastCGI and followed the guides there, but the documentation is quite awful and doesn't always line up with my environment, so I've had to put in a lot of guess and check work. I'll provide the code I've added to my config files so you see where I'm at for now
000-default in /etc/apache2/sites-enabled:
Alias /rt /opt/rt4/share/html
Alias /NoAuth/images /var/www/rt/share/html/NoAuth/images/
AddHandler fastcgi-script fcgi
ScriptAlias / /var/www/rt/sbin/rt-server.fcgi/
<Directory /opt/rt4/share/html/>
Order allow,deny
Allow from all
</Directory>
RT_SiteConfig.pm in /opt/rt4/etc:
Set($WebPath, '/rt');
Set($WebBaseURL, 'http://localhost');
If anymore information is needed, please let me know. Thanks in advance for any help!
The RT docs for web deployment give more detailed info for setting up Apache with fastcgi and for running at '/rt'. I think you'll want to initially try using the suggested Apache configurations and see if that gets you past the setup page.
(Note that those docs are available in the RT install as well in the docs directory.)