My jenkins installation on Debian was upgraded (using apt) - and now jenkins refuses to start. I can see the following in the log:
Exception in thread "main" java.lang.IllegalArgumentException:
Unrecognized option: --ajp13Port=-1
My jenkins version is 2.381. Unfortunately, I now don't know which version was installed prior to this, but it definitely worked and no config changes have been made.
How can I get it to start?
I have some Windows 2016 servers that are located behind a load balancer. I don't have any control over the load balancer other than being able to connect to servers via it. This whole set up is in the cloud. I need to enable RDP connection on the windows servers - to allow connections for management/monitoring/etc. As I don't have any control over the load balancer, I cannot put any security/firewall/etc. rules on it. If I allow RDP connections to the servers, that means that anybody from anywhere can RDP onto them (provided they have credentials, of course, but that doesn't help in case of any 0-day in RDP protocol for example).
When I RDP onto these servers, I have to specify a load balancer cookie indicating which server I'm connecting to - that's the only control I have.
I can set up firewall rules on the servers themselves to only allow RDP connection from certain IP addresses. But when I enable RDP and connect to the server, the RDP session lists the remote address as the internal IP of the load balancer (i.e. 10.x.x.x) .
So, is there any way I can restrict RDP on servers to specific external IP addresses?
Our artifactory installation has 500GB data disk allocated to it. Yesterday it ran out of space and went about cleaning up old artifacts (something I thought was being done automatically but it wasn't). After deleting over 200GB worth of old artifacts, I could see trash can size reported as 228 GB. I then emptied the trash can and manually forced the garbage collection run. I also manually ran "Prune unreferenced data". Now I'm trying to understand why the actual space on the disk is not being freed up. Artifactory now reports the following:
How can I free up the 200+ GB of disk space that shouldn't be used any more?
I'm struggling to get the networking working working on a linux VM. As is after the setup, I have this ifconfig:
# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.19.190.144 netmask 255.255.0.0 broadcast 172.19.255.255
inet6 fe80::215:5dff:febe:6707 prefixlen 64 scopeid 0x20<link>
ether 00:15:5d:be:67:07 txqueuelen 1000 (Ethernet)
RX packets 30629 bytes 3428768 (3.2 MiB)
RX errors 0 dropped 409 overruns 0 frame 0
TX packets 351 bytes 53232 (51.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 78 bytes 6600 (6.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 78 bytes 6600 (6.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
And this routing table:
# ip route
default via 172.19.190.1 dev eth0 proto static metric 100
172.19.0.0/16 dev eth0 proto kernel scope link src 172.19.190.144 metric 100
With this setup, I can ping the gateway and external internet hosts, but I cannot ping hosts on 172.19.180.x subnet, getting "host unreachable".
When I then manually do
# ip route add 172.19.0.0/16 via 172.19.190.1 dev eth0
Then everything works as expected. I now add this line into /etc/sysconfig/network-scripts/route-eth0:
172.19.0.0/16 via 172.19.190.1
After the reboot, my routing table looks like this:
# ip route
default via 172.19.190.1 dev eth0 proto static metric 100
172.19.0.0/16 dev eth0 proto kernel scope link src 172.19.190.144 metric 100
172.19.0.0/16 via 172.19.190.1 dev eth0 proto static metric 100
And I again cannot get to 172.19.180.x subnet. The difference between this and the manual addition with ip route add is that the last line has proto static metric 100 at the end, whereas with the manual way it doesn't.
What do I need to do to get everything working on a reboot?
UPDATE: here's my ifcfg-eth0 file:
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=eth0
UUID=.... (masked)
DEVICE=eth0
ONBOOT=yes
IPADDR=172.19.190.144
PREFIX=16
GATEWAY=172.19.190.1
DNS1=172.19.190.240
DNS2=172.19.190.242
UPDATE2:
If I remove the second route (... src 172.19.190.144...) and only leave one default, then everything work correctly. Then the question becomes: where does the second route come from and how do I get rid of it?
The TLS (SSL) certificate on one of my site expired yesterday. I obtained a new one - and installed it on the site (running on Debian 9 under nginx). Now when I access the site from a windows or mac, the certificate is processed correctly and everything is hunky-dory.
At the same time, I have a service that runs on this same server and connects to this same site. Since the certificate update, this service started failing. Trying to debug this, I came to realise that the system itself where the certificate is installed does not trust the issuer. Using wget, I get this error:
Certificate hasn't got a known issuer
Using curl I get this error:
SSL certificate problem: unable to get local issuer certificate
This seems to point to a missing ca certificate on the system. I tried running update-ca-certificates and dpkg-reconfigure ca-certificates. Both processes complete successfully, however the problem persists.
Here's the certificate details from Chrome on mac:
I attempted to manually add root issuer certificate to the ca-certs store and update-ca-certificate, however that resulted in a warning of a duplicate certificate.
How can I get this resolved? Disabling certificate check is NOT an option; accessing the site over HTTP is not an option either.
I've looked at dozens of other questions and references on the web - and by all my calculations, my setup should work, but it doesn't.
I have nginx installation with php-fpm. If I try to access a .php file, it runs correctly and I get the correct results. I got this in my config file:
location ~ \.php$ {
try_files $uri =404;
fastcgi_pass unix:/var/run/php5-fpm.sock;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
}
Now, I want to setup my web app so that /somedir/file automatically executes /somdir/file.php while still displaying /somdir/file in the browser's address bar. So I modified my config to contain the following:
location / {
try_files $uri $uri/ $uri.php?query_string
}
This kind of works, that is, the server does access the .php file. Yet, instead of executing it using the existing location ~ \.php$ block above, it simply spits the php source code as the download into the browser. If I append the .php manually to the requested URL, then the php is executed.
It feels as if once the server matches try_files to $uri.php, it then does not do another pass at locations to see that what it needs to do with the php files. I tried putting the php block above and below the location /, but it makes no difference.
How can I get the php to be executed?
I'm having the most weird thing happening with my web server. It's Apache 2 with SSL. To simplify, here's why my config looks like (example.com refers to my own domain, of course):
<VirtualHost *:80>
ServerName example.com
ServerAlias www.example.com
Redirect 301 / https://example.com/
</VirtualHost>
<VirtualHost *:443>
ServerName example.com
DocumentRoot /var/www/example
... #options and allow/deny for directories
... #logging settings
SSLEngine on
... #ssl settings
</VirtualHost>
<VirtualHost *:443>
ServerName www.example.com
Redirect 301 / https://example.com/
SSLEngine on
... #ssl settings
</VirtualHost>
Essentially, what it does is redirect all non-https traffic to https and redirects www.example.com to example.com - so far, so good.
This works for all browsers on all platforms - with one exception: Safari on iPad. Safari on mac works fine; other browsers on ipad work fine, but on Safari on ipad I get "Safari cannot open the page because too many redirects occurred".
Now, the only redirect I have in my setup (on https) is from www.example.com to example.com. I added %{Host}i to the access log - and I can see that the requests contain correct hostname and resource.
At this point I am completely stumped. I don't know where or what else to look at. My client mainly uses ipads, so ignoring it isn't an option.
Any ideas are greatly appreciated.
EDIT:
I changed the SSL configuration to this:
<VirtualHost *:80>
ServerName example.com
ServerAlias www.example.com
Redirect 301 / https://example.com/
</VirtualHost>
<VirtualHost *:443>
ServerName example.com
ServerAlias www.example.com
DocumentRoot /var/www/example
... #options and allow/deny for directories
... #logging settings
SSLEngine on
... #ssl settings
</VirtualHost>
Now there are no redirects in the config at all. I cleared all settings, history and stored data from the ipad - and it's still redirecting!
I have my domain served by two servers with different IP addresses: one for main website and another for online shop. When a customer places an order, among other things, an email is being sent to an internal email address [email protected]. This email is sent by the server on which the online store resides. However the email is sent to be from the customer's email address, so, for example, if [email protected] places an order, an email will be sent from the online store to [email protected] with details of the order, pretending to be from [email protected].
On my mail server, SpamAssassin rejects these emails though because they fail SPF validation check, specifically, I get error message stating that store.example.com is not allowed to send mail from example.org (this is easy to understand, as my online store will not be included into example.org SPF record).
I am administering example.com on behalf of a client - and the client states that emails from the store need to arrive in this format (i.e. from [email protected] as opposed to a generic [email protected]). How can I configure SpamAssassin (via cPanel or, if necessary via back end) to accept messages delivered by store.example.com?
Our business email is hosted on Google apps. In addition, our web server may also send email. Currently our SPF record in DNS looks like this:
domain.com. IN TXT "v=spf1 a include:_spf.google.com -all"
This is all fine, however now we've outsourced our email list management to another company and we need to include a second domain with include. So, I'm looking for something like:
domain.com. IN TXT "v=spf1 a include:_spf.google.com include:otherdomain.com -all"
What is the correct syntax for this? Many thanks!