Question #13938
closed
Technique Editor Error
Description
Hello,
After Rudder-server 5.0.3 install, i can't anymore create a new Technique.
HTTP ERROR 404
Problem accessing /ncf-builder/. Reason:
Not Found
Could you help to fix this issue please ?
I tried to fix it by following descriptions in the website http://www.ncf.io/pages/ncf-builder.html
but it doesn't solve the problem.
Thank you !
Best regards
Files
Updated by Vincent MEMBRÉ almost 6 years ago
- Category set to Web - Technique editor
- Target version set to 5.0.4
Hello sat!
Thanks for reporting your issue :)
So tu understand correctly, do you upgraded your Rudder from an older version ? as I understand, you could do it before but after install of 5.0.3 it broke.
On which distribution Rudder server is installed ?
Do you mind sending me debug informations ? you can get a zip with all useful informations at the bottom of the Settings -> General page with the "download debug information" button
Updated by sat raoeli almost 6 years ago
- File debug-info-lpn3e73.tlt-2018-12-04-140421.tar.gz added
We are in CentOS Linux release 7.2.1511 and have upgraded from Rudder Server 4.3.0. The Technique Editor worked very well.
Please see the attached debug information file.
Thanks
Updated by Alexis Mousset almost 6 years ago
- File deleted (
debug-info-lpn3e73.tlt-2018-12-04-140421.tar.gz)
Updated by Vincent MEMBRÉ almost 6 years ago
Is rudder web app working correctly ? from what I see, the webapp is restarting every 5 minutes since it cannot access its databases ?
Do you have logs of your upgrade ? if you have lost your history you may find it in /var/log/yum.log files
Updated by sat raoeli almost 6 years ago
Vincent,
You're right... i have to sign in every 5 min to the rudder web app.
You can see in attached file the yum log about the upgrade.
But in think, the bellow error in the cfengine\previous log file could help :
R: @@server-roles@@result_error@@server-roles@@server-roles-directive@@0@@Check rudder status@@None@@2018-12-04 13:00:15+00:00##root@#The http://localhost:8080/rudder/api/status web interface failed to respond for the second time. Restarting jetty NOW! error: Method 'generic_alive_check' failed in some repairs error: Finished command related to promiser '/usr/bin/curl --proxy '' --max-time 240 -s http://localhost:8080/endpoint/api/status |/bin/grep -q OK' -- an error occurred, returned 1 R: @@server-roles@@result_error@@server-roles@@server-roles-directive@@0@@Check endpoint status@@None@@2018-12-04 13:00:15+00:00##root@#The http://localhost:8080/endpoint/api/status web interface failed to respond for the second time. Restarting jetty NOW! error: Method 'generic_alive_check' failed in some repairs
Perhaps my issue is from that, as Rudder web server is not listening on localhost but only on the lpn3e73.tlt interface :
[root@lpn3e73 log]# lsof -i:8080 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java 24614 root 187u IPv6 139735512 0t0 TCP lpn3e73.tlt:webcache (LISTEN)
How could i force jetty to use lpn3e73.tlt and never localhost ?
Updated by Vincent MEMBRÉ almost 6 years ago
Can it resolve localhost as 127.0.0.1?
Can you add
127.0.0.1 localhost
to /etc/hosts and restart rudder and httpd services ?
Updated by sat raoeli almost 6 years ago
Yes,
[root@lpn3e73 ~]# ping localhost PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.044 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.046 ms --- localhost ping statistics ---
But Rudder server is not listening from "localhost" :
[root@lpn3e73 ~]# wget http://localhost:8080/rudder/ --2018-12-04 15:57:42-- http://localhost:8080/rudder/ Resolving localhost (localhost)... ::1, 127.0.0.1 Connecting to localhost (localhost)|::1|:8080... failed: Connection refused. Connecting to localhost (localhost)|127.0.0.1|:8080... failed: Connection refused.
but only on lpn3e73.tlt interface :
[root@lpn3e73 ~]# wget http://lpn3e73.tlt:8080/rudder/ --2018-12-04 15:57:49-- http://lpn3e73.tlt:8080/rudder/ Resolving lpn3e73.tlt (lpn3e73.tlt)... 10.36.209.210 Connecting to lpn3e73.tlt (lpn3e73.tlt)|10.36.209.210|:8080... connected. HTTP request sent, awaiting response... 200 OK Length: 6311 (6.2K) [text/html] Saving to: âindex.htmlâ 100%[=====================================================================================================>] 6,311 --.-K/s in 0s 2018-12-04 15:57:49 (325 MB/s) - âindex.htmlâ saved [6311/6311]
So i think if i can modify rudder server settings to never use 'localhost' this could fix the issue. Don't you ?
Updated by Vincent MEMBRÉ almost 6 years ago
Changing localhost on all checks and config would be a huge change, since a lot of configuration and checks assume that the webapp can be contacted on localhost
Are you sure it's not a new install on a new machine ? maybe some configuration are different especially ip side, maybe a firewall blocking localhost ?
What are a the outputs of:
ip a
and
netstat -taupen
Updated by sat raoeli almost 6 years ago
Hi Vincent,
It's not a new machine but the installation is like a new one as i uninstalled all components of previous Rudder version 4.3.0 before installing the 5.0.3.
I deleted folders /opt/rudder and /var/rudder before and reinitialize ldap base.
No firewall is running in the machine...
I will try a new install again and on post installation command
/opt/rudder/bin/rudder-init
Do you confim that i have nothing special to do to permit the webapp listening on "localhost" ?
Updated by sat raoeli almost 6 years ago
Hi again Vincent !
I've got a new machine and after reinstalling rudder-server (5.0.3).
The Technique Editor seems OK. No more error.
But, when i want to go to RuleManagement, i've got this error message :
error while fetching compliances >- Error when trying to retrieve change reports <- ERROR: relation "ruddersysevents" does not exist Position: 134
Have i missed something ?
Updated by Vincent MEMBRÉ almost 6 years ago
Hi :)
is package rudder-reports correctly installed on your rudder-server-root install? "ruddersysevents" is a table used to store reporting informations and it seems to be missing.
I can give you the commands to initialize it, but in the meantime, can you attach /var/log/rudder/webapp/2018_12_13.stderrout.log file or send it to me by email (vme@rudder.io)
Updated by sat raoeli almost 6 years ago
Vincent,
The user "rudder" couldn't connect to postgres database, i've fix it and everything seems ok.
Thank you very much for your help !
Please close this "Demande".
Updated by Vincent MEMBRÉ almost 6 years ago
- Status changed from New to Resolved
Poor "rudder" user :(
I close this demand :) don't hesitate to open an other issue or to come on a webchat either on irc or on gitter https://gitter.im/normation/rudder