Apache seems to have the port blocked. I removed my thumbdrive earlier after using XAMPP on it successfully that had it on it and went somewhere then came back & well all the sudden it will not work. I am getting the below error messages after I push the start button.
View 1 RepliesI using apache server and I have the following lines in my code.
Code:
import logging
LOG = logging.getLogger(__name__)
msg = "This is level info"
LOG.info(msg)
Here the message "This is level info" must come in level 'info' in the apache2/error.log
But I get the message in file "apache2/error.log" as follows:
[Thu Apr 02 12:57:59 2015] [error] This is level info
Since the message is logged with LOG.info it is expected to be of class [info]
They started blocking my Port 25, so I made an iptables entry on my server to redirect posrt 26 to port 25 so I could set my outgoing mail for my server (from Outlook) to port 26. But one day later teh bastards are blocking my port 26 too! Guess they just don't want ANY outbound mail send from anything but their servers! If I had any other option, I'd dump Comcast in a heartbeat!
View 3 Replies View RelatedBeen running CSF and very happy with. Just wondering if anyone periodically has to restart CSF because it is blocking something it shouldn't? For example, I have port 5151 open in csf.conf, suddenly (at random) the port will be blocked. I restart CSF and everything is fine.
View 4 Replies View Relatedi have a customer whos isp blocked both port 110 and 25, so far i was able to fix the problem with sending e-mails (port 25) but i cant see where do i change or add another port for receive email on my server, and since i cant do it... there is no point on opening a port in the firewall.
View 10 Replies View RelatedI want to check if certain port is open and not blocked by my ISP how can I do that?
let's say I want to check if PPTP VPN port is open what software show me these info
I'm runnung a server with Apache2 (Apache/2.2.16 (Debian 6.0))
I would like Apache2 listen on port 8080 for IPv4 and on port 80 for IPv6.
This is what I have now:
/etc/apache2/ports.conf
Does anyone know what the following events in /var/log/messages mean. It looks like some sort of failure on the ata bus. Does the last line mean that it successfully wrote all data using the cache, or could there be data loss?
The output of smartctl looks ok for the disk.
Code:
Jul 26 16:44:35 server1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Jul 26 16:44:35 server1 kernel: ata1.00: cmd c8/00:08:9d:e2:8a/00:00:00:00:00/ec tag 0 cdb 0x0 data 4096 in
Jul 26 16:44:35 server1 kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 26 16:44:42 server1 kernel: ata1: port is slow to respond, please be patient (Status 0xd0)
Jul 26 16:45:05 server1 kernel: ata1: port failed to respond (30 secs, Status 0xd0)
Jul 26 16:45:05 server1 kernel: ata1: soft resetting port
Jul 26 16:45:10 server1 kernel: ata1.00: revalidation failed (errno=-2)
Jul 26 16:45:10 server1 kernel: ata1: failed to recover some devices, retrying in 5 secs
Jul 26 16:45:15 server1 kernel: ata1: soft resetting port
Jul 26 16:45:15 server1 kernel: ata1.00: configured for UDMA/133
Jul 26 16:45:15 server1 kernel: ata1: EH complete
Jul 26 16:45:15 server1 kernel: SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
Jul 26 16:45:15 server1 kernel: SCSI device sda: drive cache: write back
I just ran 'rkhunter -c --quiet' and this is the error messages I got:
Line:
Warning: This operating system is not fully supported!
Line: Warning: This operating system is not fully supported!
Warning: Cannot find md5_not_known
Some errors has been found while checking. Please perform a manual check on this machine debian
Is this something I should be worried about??
I'm running CentOS 5.
This is our first installation of Plesk Panel.
In our root directory have the Logs folder, but do not know how to find the log file to access the error messages that may be generated one.
I have a Plesk 11.5 server that someone made changes to in IIS to allow web site users to turn the sending of detailed error messages on and off from a web.config file. Unfortunately now none of the sites will send detailed error messages to the browser no matter what is done. The person that made the changes to IIS did not document them properly and cannot tell me what exactly they changed. None of the obvious settings have made an effect on the problem.
View 1 Replies View Relatedafter the update i've got many errors in plesk panel, for example:
- change webhosting settings (like password, etc)
Internal error.
ERROR: Call to a member function getWebServerFPAdminSysUser() on a non-object (Apache.php:738)
- click on server components in server manager:
ERROR: Call to a member function getWebServerPackage() on a non-object (class.ServiceControl.php:76)
I have 2.4.3 (Win-64) installed and running. When it starts up, I get a command prompt window that has messages in it, but the window closes so quickly, I can't read the messages. They don't appear in the log. I have tried to manually start the server, but when I do, the messages do not appear!
How can I get that window to stay open or where can I see those messages?
Plesk 12 is used, latest #MU on CentOS 6.5 final.
Maillog is full of messages like:
Mar 31 14:56:52 hosting plesk sendmail[1177]: _mh_fork(): Error occured during waiting the child process with pid: 1178: No child processes
Mar 31 14:56:52 hosting plesk sendmail[1177]: Error during 'check-quota' handler
Mar 31 14:56:52 hosting plesk sendmail[1177]: Unable to get sender domain by sender mailname
[Code]....
How to hide from our clients (end users: Plesk customers/resellers) any message related to Apache configuration files failed, like this one:
"Error: Web server configuration for some of your domains may be inconsistent. Please contact server administrator to resolve the problem."
We already see the message within Plesk admin interface, so our customers don't really need to see that, as there's nothing they can do for that.
We have following error when try to start apf in one of our vps:
apf(3126): {glob} opening inbound tcp port 80 on 0/0
apf(3126): {glob} opening inbound tcp port 110 on 0/0
apf(3126): {glob} opening inbound tcp port 111 on 0/0
apf(3126): {glob} opening inbound tcp port 143 on 0/0
apf(3126): {glob} opening inbound tcp port 443 on 0/0
apf(3126): {glob} opening inbound tcp port 465 on 0/0
apf(3126): {glob} opening inbound tcp port 623 on 0/0
apf(3126): {glob} opening inbound tcp port 918 on 0/0
apf(3126): {glob} opening inbound tcp port 993 on 0/0
apf(3126): {glob} opening inbound tcp port 995 on 0/0
apf(3126): {glob} opening inbound tcp port 2082 on 0/0
apf(3126): {glob} opening inbound tcp port 2083 on 0/0
apf(3126): {glob} opening inbound tcp port 2086 on 0/0
apf(3126): {glob} opening inbound tcp port 2087 on 0/0
apf(3126): {glob} opening inbound tcp port 2095 on 0/0
apf(3126): {glob} opening inbound tcp port 2096 on 0/0
apf(3126): {glob} opening inbound tcp port 3306 on 0/0
apf(3126): {glob} opening inbound tcp port 3389 on 0/0
apf(3126): {glob} opening inbound tcp port 6666 on 0/0
apf(3126): {glob} opening inbound tcp port 7776 on 0/0
apf(3126): {glob} opening inbound tcp port 7777 on 0/0
apf(3126): {glob} opening inbound tcp port 7778 on 0/0
apf(3126): {glob} opening inbound tcp port 7779 on 0/0
apf(3126): {glob} opening inbound tcp port 8887 on 0/0
apf(3126): {glob} opening inbound tcp port 8888 on 0/0
apf(3126): {glob} opening inbound tcp port 8889 on 0/0
apf(3126): {glob} opening inbound udp port 21 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening inbound udp port 53 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening inbound udp port 161 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening inbound udp port 465 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening inbound udp port 623 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening inbound udp port 873 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 21 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 22 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 25 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 26 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 27 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 37 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 43 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 53 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 80 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 110 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 113 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 443 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 465 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 623 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 873 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 2089 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound tcp port 3389 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound udp port 20 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound udp port 21 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound udp port 53 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound udp port 161 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound udp port 465 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound udp port 623 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening outbound udp port 873 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening inbound icmp type 3 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening inbound icmp type 5 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening inbound icmp type 11 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening inbound icmp type 0 on 0/0
iptables: Unknown error 4294967295
apf(3126): {glob} opening inbound icmp type 30 on 0/0
I installed apache, and it seems to be running fine.
I can view the website when I do domain.com:81
However when I solely type domain.com I can't view the page. Why is that, and how can I fix this?
I'm trying to compile Apache 2.4 on a MAC OS X 10.9 with XCode installed and it keeps telling me the gcc in it cannot create executables, where I can find documentation about how to do this?
I tried the MAMP apps, but I don't want that, I want to have the MAC to act as a server without paying the $19.99 Apple asks for the server software.
How can I set a certain folder under my www folder to use a non standard port, 6767 instead of 80. I am running apache 2.
I tried putting the following in my httpd.conf with no luck, each time when I attemped to restart apache I got a fatal error:
<Directory "/var/www/html/crm">
Listen 6767
</Directory>
<Directory "/var/www/html/crm">
Port 6767
</Directory>
<Directory "/var/www/html/crm">
Bind 192.168.0.200 6767
</Directory>
my apache listen at port 78, however, when I modify listen 80 and port 80 to listen 78 and port 78, restart apache, it does not work. I checked the port 78, nothing but apache there. even I modify all :80 to :78 in the httpd.conf, still does not work. there only one site on the server. there is nothing on error log file.
my system is x86_64 cento 4.4 and apache is 1.3.37.
an Apache 2.2 server suddenly quit accepting traffic on port 80. The error message was "An attempt was made to access a socket in a way forbidden by its access permissions could not bind to address 0.0.0.0:80 ".It took a while, but the server is now back up.
View 2 Replies View RelatedI have just noticed that for several days I'm constantly receiving these infos in /var/log/messages. I haven't done anything that would invoke them. How can I disable these messages? Are they anything to worry about?
Code:
Feb 6 14:28:18 server kernel: [<c014f600>] find_extend_vma+0x12/0x4f
Feb 6 14:28:18 server kernel: [<c0134383>] get_futex_key+0x39/0x108
Feb 6 14:28:18 server kernel: [<c011d305>] finish_task_switch+0x30/0x66
Feb 6 14:28:18 server kernel: [<c02cf618>] schedule+0x844/0x87a
Feb 6 14:28:18 server kernel: [<c027734b>] sys_socketcall+0x1df/0x1fb
Feb 6 14:28:18 server kernel: [<c0125bc5>] sys_gettimeofday+0x53/0xac
Feb 6 14:28:18 server kernel: [<c02d137f>] syscall_call+0x7/0xb
Feb 6 14:28:18 server kernel: [<c02d007b>] _read_lock_irq+0x4/0x1e
Feb 6 14:28:18 server kernel: Badness in dst_release at include/net/dst.h:149
Feb 6 14:28:18 server kernel: [<f8d8a555>] ip6_push_pending_frames+0x340/0x369 [ipv6]
Feb 6 14:28:18 server kernel: [<f8d9883f>] udp_v6_push_pending_frames+0x169/0x185 [ipv6]Badness in dst_release at include/net/dst.h:149
Feb 6 14:28:18 server kernel: [<c0278fa8>]
Feb 6 14:28:18 server kernel: [<f8d98e7d>] udpv6_sendmsg+0x622/0x770 [ipv6]
Feb 6 14:28:18 server kernel: [<c027a498>] __kfree_skb+0x55/0xf7
Feb 6 14:28:18 server kernel: [<c027e1b8>] skb_dequeue+0x40/0x46
Feb 6 14:28:18 server kernel: [<c027b009>] net_tx_action+0x60/0xfc
Feb 6 14:28:18 server kernel: [<c0126354>] skb_recv_datagram+0x61/0x9b
Feb 6 14:28:18 server kernel: [<c02b1ed7>] __do_softirq+0x4c/0xb1
Feb 6 14:28:18 server kernel: [<c010814b>] do_softirq+0x4f/0x56
Feb 6 14:28:18 server kernel: =======================
Feb 6 14:28:18 server kernel: [<c0107a60>] do_IRQ+0x1a2/0x1ae
Feb 6 14:28:18 server kernel: [<c02d1d3c>] udp_recvmsg+0x5f/0x271
Feb 6 14:28:18 server kernel: [<c02b7b35>] common_interrupt+0x18/0x20
Feb 6 14:28:18 server kernel: [<c02d007b>] inet_sendmsg+0x38/0x42
Feb 6 14:28:18 server kernel: [<c02757f5>] _read_lock_irq+0x4/0x1e
Feb 6 14:28:18 server kernel: sock_sendmsg+0xdb/0xf7
Feb 6 14:28:18 server kernel: [<c02757f5>] sock_sendmsg+0xdb/0xf7
Feb 6 14:28:18 server kernel: [<c011fee1>] autoremove_wake_function+0x0/0x2d
Feb 6 14:28:18 server kernel: [<c027a89e>] verify_iovec+0x76/0xc2
Feb 6 14:28:18 server kernel: [<c0276f44>] sys_sendmsg+0x1ee/0x23b
Feb 6 14:28:18 server kernel: [<c011cb7d>] activate_task+0x88/0x95
Feb 6 14:28:18 server kernel: [<c011d00a>] try_to_wake_up+0x225/0x230
Feb 6 14:28:18 server kernel: [<c011d00a>] try_to_wake_up+0x225/0x230
Feb 6 14:28:18 server kernel: [<c0170776>] inode_update_time+0x80/0x87
Feb 6 14:28:18 server kernel: [<c0164748>] pipe_writev+0x310/0x31c
Feb 6 14:28:18 server kernel: [<c02cf622>] schedule+0x84e/0x87a
Feb 6 14:28:18 server kernel: [<c027734b>] sys_socketcall+0x1df/0x1fb
Feb 6 14:28:18 server kernel: [<c0125bc5>] sys_gettimeofday+0x53/0xac
Feb 6 14:28:18 server kernel: [<c02d137f>] syscall_call+0x7/0xb
Feb 6 14:28:18 server kernel: [<c02d007b>] _read_lock_irq+0x4/0x1e
Feb 6 14:28:18 server kernel: Badness in dst_release at include/net/dst.h:149
Feb 6 14:28:18 server kernel: [<f8d98ef7>] udpv6_sendmsg+0x69c/0x770 [ipv6]
Feb 6 14:28:18 server kernel: [<c027a498>] skb_dequeue+0x40/0x46
Feb 6 14:28:18 server kernel: [<c027b009>] skb_recv_datagram+0x61/0x9b
Feb 6 14:28:18 server kernel: [<c02b1ed7>] udp_recvmsg+0x5f/0x271
Feb 6 14:28:18 server kernel: [<c02b7b35>] inet_sendmsg+0x38/0x42
Feb 6 14:28:18 server kernel: [<c02757f5>] sock_sendmsg+0xdb/0xf7
Feb 6 14:28:18 server kernel: [<c02757f5>] sock_sendmsg+0xdb/0xf7
Feb 6 14:28:18 server kernel: [<c011fee1>] autoremove_wake_function+0x0/0x2d
Feb 6 14:28:18 server kernel: [<c027a89e>] verify_iovec+0x76/0xc2
Feb 6 14:28:18 server kernel: [<c0276f44>] sys_sendmsg+0x1ee/0x23b
Feb 6 14:28:18 server kernel: [<c011cb7d>] activate_task+0x88/0x95
Feb 6 14:28:18 server kernel: [<c011d00a>] try_to_wake_up+0x225/0x230
Feb 6 14:28:18 server kernel: [<c011d00a>] try_to_wake_up+0x225/0x230
Feb 6 14:28:18 server kernel: [<c0170776>] inode_update_time+0x80/0x87
Feb 6 14:28:18 server kernel: [<c0164748>] pipe_writev+0x310/0x31c
Feb 6 14:28:18 server kernel: [<c02cf622>] schedule+0x84e/0x87a
Feb 6 14:28:18 server kernel: [<c027734b>] sys_socketcall+0x1df/0x1fb
Feb 6 14:28:18 server kernel: [<c0125bc5>] sys_gettimeofday+0x53/0xac
Feb 6 14:28:18 server kernel: [<c02d137f>] syscall_call+0x7/0xb
Feb 6 14:28:18 server kernel: [<c02d007b>] _read_lock_irq+0x4/0x1e
After migrating our existing client base from legacy Plesk 9.x servers and Expand to PPA, clients phoned in with mail sending problems. These clients are using submission port 587 because their ISPs intercept port 25.
Existing client, Outlook error message:
"None of the authentication methods supported by this client are supported by your server"
Testing with Thunderbird, error message:
"An error occurred while sending mail. The mail server responded: 5.7.0 Must issue a STARTTLS command first. Please verify that your email address is correct in your Mail preferences and try again."
It seems a "fresh" PPA requires STARTTLS on e-mail clients. It is furthermore confirmed that Thunderbird detects the e-mail server settings as dependant on TLS.
The problem is that TLS doesn't seem to work properly by default.
In order to preserve our existing customer base, we follow: [URL] ....
Bottom line, in your /etc/postfix/master.cf, change the line that says "submission" from this:
submission inet n – - – - smtpd -o smtpd_enforce_tls=yes -o smtpd_tls_security_level=encyrpt -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions=permit_sasl_authenticate d,reject -o smtpd_sender_restrictions= -o smtpd_proxy_filter=127.$
to this:
submission inet n – - – - smtpd -o smtpd_enforce_tls=no -o smtpd_tls_security_level=may -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions=permit_sasl_authenticate d,reject -o smtpd_sender_restrictions= -o smtpd_proxy_filter=127.$
then do:
/etc/init.d/postfix reload
This is just a quick fix to get you going and stop the phones from ringing. Ideally we would like to re-enable TLS and have information as to why it is not working.
I use url http://myurl:8020/ERC to access application and I am able to. But I dont want to use port number in the URL.Would like to access application using http://myurl/ERC . I referred to one of the post and added below entries to httpd.conf file.
ProxyRequests Off
ProxyPass /ERC http://myurl:8020/ERC
ProxyPassReverse /ERC http://myurl:8020/ERC
But I am still not able to access http://myurl/ERC.LoadModule entries are enabled and I have restarted apache.