I am trying to make an internal call from extension 1000 to 1001 and backwaards. 1000->1001 works and i can answer/hangup. 1001->1000 doesnt work. Can anyone assist me please ? Thank you. Here's the log:
freeswitch#ubuntu> 2015-10-24 19:54:48.252475 [NOTICE] switch_channel.c:1053 New Channel sofia/internal/1001#192.168.20.199 [81ce2ac0-dbf9-4102-9885-a0a4c6e0541e]
2015-10-24 19:54:48.272476 [INFO] mod_dialplan_xml.c:558 Processing 1001 <1001>->1000 in context default
2015-10-24 19:54:48.272476 [INFO] switch_ivr_async.c:3631 Bound B-Leg: *1 execute_extension::dx XML features
2015-10-24 19:54:48.272476 [INFO] switch_ivr_async.c:3631 Bound B-Leg: *2 record_session::/usr/local/freeswitch/recordings/1001.2015-10-24-19-54-48.wav
2015-10-24 19:54:48.272476 [INFO] switch_ivr_async.c:3631 Bound B-Leg: *3 execute_extension::cf XML features
2015-10-24 19:54:48.272476 [INFO] switch_ivr_async.c:3631 Bound B-Leg: *4 execute_extension::att_xfer XML features
2015-10-24 19:54:48.292436 [NOTICE] switch_channel.c:1053 New Channel sofia/internal/sip:1000#147.229.148.23:52888 [78eeebd6-be44-412b-8fe7-08ce94b21836]
2015-10-24 19:54:48.292436 [NOTICE] sofia.c:7112 Hangup sofia/internal/sip:1000#147.229.148.23:52888 [CS_CONSUME_MEDIA] [NORMAL_TEMPORARY_FAILURE]
2015-10-24 19:54:48.292436 [NOTICE] switch_ivr_originate.c:2707 Cannot create outgoing channel of type [user] cause: [NORMAL_TEMPORARY_FAILURE]
2015-10-24 19:54:48.292436 [INFO] mod_dptools.c:3234 Originate Failed. Cause: NORMAL_TEMPORARY_FAILURE
2015-10-24 19:54:48.292436 [NOTICE] switch_core_session.c:1632 Session 24 (sofia/internal/sip:1000#147.229.148.23:52888) Ended
2015-10-24 19:54:48.292436 [NOTICE] switch_core_session.c:1636 Close Channel sofia/internal/sip:1000#147.229.148.23:52888 [CS_DESTROY]
2015-10-24 19:54:48.292436 [NOTICE] sofia_media.c:92 Pre-Answer sofia/internal/1001#192.168.20.199!
2015-10-24 19:54:48.292436 [NOTICE] mod_dptools.c:1258 Channel [sofia/internal/1001#192.168.20.199] has been answered
2015-10-24 19:54:49.312660 [NOTICE] switch_channel.c:1053 New Channel loopback/app=voicemail:default 192.168.20.199 1000-a [ff3ba363-2c45-4466-b6d1-d05f507b882e]
2015-10-24 19:54:49.312660 [NOTICE] switch_channel.c:1051 Rename Channel loopback/app=voicemail:default 192.168.20.199 1000-a->loopback/voicemail-a [ff3ba363-2c45-4466-b6d1-d05f507b882e]
2015-10-24 19:54:49.312660 [NOTICE] switch_channel.c:1053 New Channel loopback/voicemail-b [15c11755-1891-4530-ac42-4f68b21c4abf]
2015-10-24 19:54:49.312660 [NOTICE] mod_loopback.c:947 Pre-Answer loopback/voicemail-a!
2015-10-24 19:54:49.312660 [NOTICE] mod_dptools.c:1293 Pre-Answer loopback/voicemail-b!
2015-10-24 19:54:52.452289 [NOTICE] sofia.c:926 Hangup sofia/internal/1001#192.168.20.199 [CS_EXECUTE] [NORMAL_CLEARING]
2015-10-24 19:54:52.452289 [NOTICE] switch_ivr_bridge.c:751 Hangup loopback/voicemail-a [CS_EXCHANGE_MEDIA] [ORIGINATOR_CANCEL]
2015-10-24 19:54:52.452289 [NOTICE] mod_loopback.c:553 Hangup loopback/voicemail-b [CS_EXECUTE] [ORIGINATOR_CANCEL]
2015-10-24 19:54:52.452289 [NOTICE] switch_core_session.c:1632 Session 26 (loopback/voicemail-b) Ended
2015-10-24 19:54:52.452289 [NOTICE] switch_core_session.c:1636 Close Channel loopback/voicemail-b [CS_DESTROY]
2015-10-24 19:54:52.452289 [NOTICE] switch_core_session.c:1632 Session 23 (sofia/internal/1001#192.168.20.199) Ended
2015-10-24 19:54:52.452289 [NOTICE] switch_core_session.c:1636 Close Channel sofia/internal/1001#192.168.20.199 [CS_DESTROY]
2015-10-24 19:54:52.452289 [NOTICE] switch_core_session.c:1632 Session 25 (loopback/voicemail-a) Ended
2015-10-24 19:54:52.452289 [NOTICE] switch_core_session.c:1636 Close Channel loopback/voicemail-a [CS_DESTROY]
It was a firewall problem. It works now.
Are you sure that user 1000 is registered when you call it? (You can list the registered users from cli).
Another possible reason might be that there are some special users in the 1001-1009 range. You might try using different usernames.
If still doesn't work, post some more detailed logs (you should increase the debug/log levels).
Related
I'm running Debian 10 with bitcoind configured as a systemd service that accesses the tor service via localhost. Every reboot the bitcoind error log is filled with the following, and tor services seem to be stuck in a non-working state.
2020-11-18T03:38:30Z connect() to 127.0.0.1:9050 failed after select(): Connection refused (111)
2020-11-18T03:38:30Z connect() to 127.0.0.1:9050 failed after select(): Connection refused (111)
2020-11-18T03:38:31Z connect() to 127.0.0.1:9050 failed after select(): Connection refused (111)
2020-11-18T03:38:31Z connect() to 127.0.0.1:9050 failed after select(): Connection refused (111)
Upon startup systemctl status tor returns the following, indicating tor started successfully
tor.service - Anonymizing overlay network for TCP (multi-instance-master)
Loaded: loaded (/lib/systemd/system/tor.service; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2020-11-17 19:54:04 PST; 4min 19s ago
Process: 413 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
Main PID: 413 (code=exited, status=0/SUCCESS)
Nov 17 19:54:04 cryptoDaemon systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)...
Nov 17 19:54:04 cryptoDaemon systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master).
However tail -f /var/log/tor/notices.log indicates tor hasn't started. There are no entries after the reboot.
If I restart tor.service with sudo systemctl restart tor the error immediately disappears and bitcoind starts to function over tor correctly. This indicates to me that the tor service itself is not starting properly after reboot.
After restarting the service /var/log/notices.log gets new entries:
Nov 17 20:02:22.000 [notice] Tor 0.3.5.10 opening log file.
Nov 17 20:02:22.875 [notice] We compiled with OpenSSL 1010104f: OpenSSL 1.1.1d 10 Sep 2019 and we are running with OpenSSL 1010107f: OpenSSL 1.1.1g 21 Apr 2020. These two versions should be binary compatible.
Nov 17 20:02:22.877 [notice] Tor 0.3.5.10 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1g, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
Nov 17 20:02:22.877 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Nov 17 20:02:22.877 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Nov 17 20:02:22.877 [notice] Read configuration file "/etc/tor/torrc".
Nov 17 20:02:22.881 [notice] You configured a non-loopback address '10.1.10.20:9050' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Nov 17 20:02:22.881 [notice] Opening Socks listener on 127.0.0.1:9050
Nov 17 20:02:22.881 [notice] Opened Socks listener on 127.0.0.1:9050
Nov 17 20:02:22.881 [notice] Opening Control listener on 127.0.0.1:9051
Nov 17 20:02:22.881 [notice] Opened Control listener on 127.0.0.1:9051
Nov 17 20:02:22.881 [warn] Unable to make /var/lib/tor group-readable: Permission denied
Nov 17 20:02:22.881 [warn] Unable to make /var/lib/tor group-readable: Permission denied
Nov 17 20:02:22.000 [notice] Not disabling debugger attaching for unprivileged users.
Nov 17 20:02:22.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Nov 17 20:02:23.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Nov 17 20:02:23.000 [notice] Bootstrapped 0%: Starting
Nov 17 20:02:23.000 [notice] Starting with guard context "default"
Nov 17 20:02:23.000 [notice] Signaled readiness to systemd
Nov 17 20:02:24.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Nov 17 20:02:24.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Nov 17 20:02:24.000 [notice] Opening Control listener on /run/tor/control
Nov 17 20:02:24.000 [notice] Opened Control listener on /run/tor/control
Nov 17 20:02:24.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Nov 17 20:02:25.000 [notice] Bootstrapped 100%: Done
Further investigation reveals that tor is not starting at boot. /var/log/tor/debug.log is empty after reboot. I can even run systemctl start tor and it starts. systemctl start tor won't mess with a service that is already started, so for some reason systemd isn't starting tor, despite it being enabled. Just for fun I disabled with systemctl disable tor and re-enabled, but to no avail.
Any ideas why tor doesn't start?
I also use this server as a Tor SOCKS proxy on the LAN using SOCKSPORT IP.OF.SERVER:9050 in torrc. disabling this and the associated SOCKSPolicy accept IP.OF.SERVER/24 fixed the issue. If anybody has any insight as to why tor behaves this way and doesn't log why, it'd be appreciated.
I fixed it by overriding the systemd configuration for the tor service since i Need the tor Proxy to listen to an actual network interface.
/etc/systemd/system/tor#default.service.d/override.conf
[Unit]
After=network.target nss-lookup.target network-online.target
Wants=network-online.target
Easy way to create the file is systemctl edit tor#default.service
rabbitmq has connected to my ports and everything looks good so far but when i try to connect to my localhost in browser im getting this error message:
The connection was reset
The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web
so the first thing i did was go and look at my rabbitmq log and i see this:
Starting RabbitMQ 3.7.9 on Erlang 20.2.2
Copyright (C) 2007-2018 Pivotal Software, Inc.
Licensed under the MPL. See http://www.rabbitmq.com/
2019-09-15 08:06:51.710 [info] <0.240.0>
node : rabbit#bowzer
home dir : /var/lib/rabbitmq
config file(s) : (none)
cookie hash : XC8syc3LUBiQChoU4UJxPA==
log(s) : /var/log/rabbitmq/rabbit#bowzer.log
: /var/log/rabbitmq/rabbit#bowzer_upgrade.log
database dir : /var/lib/rabbitmq/mnesia/rabbit#bowzer
2019-09-15 08:06:52.982 [info] <0.248.0> Memory high watermark set to 6421 MiB (6733540556 bytes) of 16054 MiB (16833851392 bytes) total
2019-09-15 08:06:52.987 [info] <0.250.0> Enabling free disk space monitoring
2019-09-15 08:06:52.987 [info] <0.250.0> Disk free limit set to 50MB
2019-09-15 08:06:52.991 [info] <0.253.0> Limiting to approx 32668 file handles (29399 sockets)
2019-09-15 08:06:52.991 [info] <0.254.0> FHC read buffering: OFF
2019-09-15 08:06:52.991 [info] <0.254.0> FHC write buffering: ON
2019-09-15 08:06:52.993 [info] <0.240.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2019-09-15 08:06:53.164 [info] <0.240.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2019-09-15 08:06:53.164 [info] <0.240.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration.
2019-09-15 08:06:53.165 [info] <0.240.0> Priority queues enabled, real BQ is rabbit_variable_queue
2019-09-15 08:06:53.219 [info] <0.278.0> Starting rabbit_node_monitor
2019-09-15 08:06:53.241 [info] <0.306.0> Making sure data directory '/var/lib/rabbitmq/mnesia/rabbit#bowzer/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L' for vhost '/' exists
2019-09-15 08:06:53.302 [info] <0.306.0> Starting message stores for vhost '/'
2019-09-15 08:06:53.303 [info] <0.310.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_transient": using rabbit_msg_store_ets_index to provide index
2019-09-15 08:06:53.305 [info] <0.306.0> Started message store of type transient for vhost '/'
2019-09-15 08:06:53.306 [info] <0.313.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": using rabbit_msg_store_ets_index to provide index
2019-09-15 08:06:53.308 [info] <0.306.0> Started message store of type persistent for vhost '/'
2019-09-15 08:06:53.312 [warning] <0.334.0> Setting Ranch options together with socket options is deprecated. Please use the new map syntax that allows specifying socket options separately from other options.
2019-09-15 08:06:53.313 [info] <0.348.0> started TCP listener on [::]:5672
2019-09-15 08:06:53.314 [info] <0.240.0> Setting up a table for connection tracking on this node: tracked_connection_on_node_rabbit#bowzer
2019-09-15 08:06:53.314 [info] <0.240.0> Setting up a table for per-vhost connection counting on this node: tracked_connection_per_vhost_on_node_rabbit#bowzer
2019-09-15 08:06:53.315 [info] <0.33.0> Application rabbit started on node rabbit#bowzer
2019-09-15 08:06:53.375 [notice] <0.86.0> Changed loghwm of /var/log/rabbitmq/rabbit#bowzer.log to 50
2019-09-15 08:06:53.540 [info] <0.5.0> Server startup complete; 0 plugins started.
2019-09-15 08:10:51.196 [info] <0.378.0> accepting AMQP connection <0.378.0> (127.0.0.1:55986 -> 127.0.0.1:5672)
2019-09-15 08:10:51.196 [error] <0.378.0> closing AMQP connection <0.378.0> (127.0.0.1:55986 -> 127.0.0.1:5672):
{bad_header,<<"GET / HT">>}
2019-09-15 08:13:26.916 [info] <0.385.0> accepting AMQP connection <0.385.0> (127.0.0.1:55990 -> 127.0.0.1:5672)
2019-09-15 08:13:26.916 [error] <0.385.0> closing AMQP connection <0.385.0> (127.0.0.1:55990 -> 127.0.0.1:5672):
{bad_header,<<"GET / HT">>}
2019-09-15 08:13:27.007 [info] <0.389.0> accepting AMQP connection <0.389.0> (127.0.0.1:55992 -> 127.0.0.1:5672)
2019-09-15 08:13:27.007 [error] <0.389.0> closing AMQP connection <0.389.0> (127.0.0.1:55992 -> 127.0.0.1:5672):
{bad_header,<<"GET /fav">>}
so i went and checked my ports and i get this:
sudo lsof -i -p -n | grep rabbitmq:
epmd 5687 rabbitmq 3u IPv4 59822 0t0 TCP *:4369 (LISTEN)
epmd 5687 rabbitmq 4u IPv6 59823 0t0 TCP *:4369 (LISTEN)
beam.smp 5892 rabbitmq 59u IPv4 57068 0t0 TCP *:25672 (LISTEN)
beam.smp 5892 rabbitmq 69u IPv6 58166 0t0 TCP *:5672 (LISTEN)
sudo service rabbitmq-server status:
● rabbitmq-server.service - RabbitMQ broker
Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset:
Active: active (running) since Sun 2019-09-15 07:53:32 MST; 2min 19s ago
Main PID: 875 (beam.smp)
Status: "Initialized"
Tasks: 90 (limit: 4915)
CGroup: /system.slice/rabbitmq-server.service
├─ 875 /usr/lib/erlang/erts-9.2/bin/beam.smp -W w -A 64 -P 1048576 -t 500000
├─1037 /usr/lib/erlang/erts-9.2/bin/epmd -daemon
├─1387 erl_child_setup 32768
├─1691 inet_gethost 4
└─1692 inet_gethost 4
Sep 15 07:53:27 bowzer rabbitmq-server[875]: ## ##
Sep 15 07:53:27 bowzer rabbitmq-server[875]: ## ## RabbitMQ 3.7.9. Copyright (C
Sep 15 07:53:27 bowzer rabbitmq-server[875]: ########## Licensed under the MPL. See
Sep 15 07:53:27 bowzer rabbitmq-server[875]: ###### ##
Sep 15 07:53:27 bowzer rabbitmq-server[875]: ########## Logs: /var/log/rabbitmq/rabb
Sep 15 07:53:27 bowzer rabbitmq-server[875]: /var/log/rabbitmq/rabb
Sep 15 07:53:27 bowzer rabbitmq-server[875]: Starting broker...
Sep 15 07:53:32 bowzer rabbitmq-server[875]: systemd unit for activation check: "rabbit
Sep 15 07:53:32 bowzer systemd[1]: Started RabbitMQ broker.
Sep 15 07:53:33 bowzer rabbitmq-server[875]: completed with 0 plugins.
i also noticed that when others download and install the server they get 'completed with 6 plugins' and mine started with 0 plugins.
Your browser is trying to talk HTTP on port 5672 which is the AMQP port of the RabbitMQ broker.
If you want to access the management console, enable the management plugin and access it on http://your-rabbitmq-host:15672/.
in httpd error log
[Mon Apr 11 21:36:15 2016] [notice] child pid 8781 exit signal Floating point exception (8)
[Mon Apr 11 21:36:15 2016] [notice] child pid 8783 exit signal Floating point exception (8)
[Mon Apr 11 21:36:15 2016] [notice] child pid 8784 exit signal Floating point exception (8)
[Mon Apr 11 21:36:15 2016] [notice] child pid 8787 exit signal Floating point exception (8)
[Mon Apr 11 21:36:15 2016] [notice] child pid 8788 exit signal Floating point exception (8)
[Mon Apr 11 21:36:15 2016] [notice] child pid 8789 exit signal Floating point exception (8)
[Mon Apr 11 21:36:15 2016] [notice] child pid 8793 exit signal Floating point exception (8)
[Mon Apr 11 21:36:15 2016] [notice] child pid 8794 exit signal Floating point exception (8)
all of my websites under white page , but i can open my images in direct link , whats is my server problem ?
additional information
[root#server ~]# php -v
PHP 5.5.32 (cli) (built: Mar 1 2016 23:09:06)
Copyright (c) 1997-2015 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2015 Zend Technologies
with the ionCube PHP Loader (enabled) + Intrusion Protection from ioncube24.com (unconfigured) v5.0.17, Copyright (c) 2002-2015, by ionCube Ltd.
yum list installed | grep "php"
php-cli.x86_64 5.3.3-46.el6_7.1 #updates
php-common.x86_64 5.3.3-46.el6_7.1 #updates
php-intl.x86_64 5.3.3-46.el6_7.1 #updates
php-mcrypt.x86_64 5.3.3-4.el6 #epel
php-pear.noarch 1:1.9.4-4.el6 #base
I'm attempting to use Bamboo behind IIS 7. I have exhausted all of my resources so Im hoping someone here can help. After starting bamboo and trying to connect my browser eventually times out with a 503. Please note that only bamboo currently has a problem. JIRA,Confluence and Crowd all work without issue
The logs from bamboo state
jvm 1| 2010-02-13 00:02:16.256::WARN: EXCEPTION
jvm 1| java.lang.IllegalAccessError
jvm 1| at org.mortbay.jetty.ajp.Ajp13Connection.<init>(Ajp13Connection.java:51)
jvm 1| at org.mortbay.jetty.ajp.Ajp13SocketConnector.newHttpConnection(Ajp13SocketConnector.java:79)
jvm 1| at org.mortbay.jetty.bio.SocketConnector$Connection.<init>(SocketConnector.java:182)
jvm 1| at org.mortbay.jetty.bio.SocketConnector.accept(SocketConnector.java:102)
jvm 1| at org.mortbay.jetty.AbstractConnector$Acceptor.run(AbstractConnector.java:707)
jvm 1| at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520) `
and the Isapi_redirect.log states:
[Sat Feb 13 00:07:40.360 2010] [2248:5256] [info] jk_ajp_common.c (1143): (worker4) can't receive the response header message from tomcat, tomcat (127.0.0.1:8035) has forced a connection close for socket 620
[Sat Feb 13 00:07:40.360 2010] [2248:5256] [error] jk_ajp_common.c (1962): (worker4) Tomcat is down or refused connection. No response has been sent to the client (yet)
[Sat Feb 13 00:07:40.361 2010] [2248:5256] [info] jk_ajp_common.c (2447): (worker4) sending request to tomcat failed (recoverable), (attempt=1)
[Sat Feb 13 00:07:40.361 2010] [2248:3860] [info] jk_ajp_common.c (1143): (worker4) can't receive the response header message from tomcat, tomcat (127.0.0.1:8035) has forced a connection close for socket 636
[Sat Feb 13 00:07:40.361 2010] [2248:3860] [error] jk_ajp_common.c (1962): (worker4) Tomcat is down or refused connection. No response has been sent to the client (yet)
[Sat Feb 13 00:07:40.361 2010] [2248:3860] [info] jk_ajp_common.c (2447): (worker4) sending request to tomcat failed (recoverable), (attempt=1) `
I have configured Bamboo to use the jetty Configuration file per the instructions here:
http://confluence.atlassian.com/display/BAMBOO/Getting+Bamboo+Standalone+to+use+the+jetty.xml+file
I have configured my jetty.xml and added
<Call name="addConnector">
<Arg>
<New class="org.mortbay.jetty.ajp.Ajp13SocketConnector">
<Set name="port">8035</Set>
</New>
</Arg>
</Call>
The Isapi config info:
workers.properties.minimal looks like this:
#jira
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=8009
#confluence
worker.worker2.type=ajp13
worker.worker2.host=localhost
worker.worker2.port=8014
#crowd
worker.worker3.type=ajp13
worker.worker3.host=localhost
worker.worker3.port=8016
#bamboo
worker.worker4.type=ajp13
worker.worker4.host=localhost
worker.worker4.port=8035
uriworkermap.properties file:
/jira/*=worker1
/confluence/*=worker2
/crowd/*=worker3
/bamboo/*=worker4
Any Ideas?
With AJP, i don't think you're supposed to use isapi_rewrite - that's like connecting an HTTP plug to an AJP socket, its not a match.
You want an AJP connector on your IIS side:
http://tomcat.apache.org/connectors-doc/webserver_howto/iis.html
check that the version of the jetty ajp jar file matches your version of jetty
The error message I gen when I try to access the web page server "192.168.50.29/cgi-bin/tinyPL.cgi"; looks like this:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, root#localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Apache/2.2.11 (Fedora) Server at 192.168.50.29 Port 80
Error_log :
[Sat Oct 24 21:30:47 2009] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Oct 24 21:30:47 2009] [notice] Digest: generating secret for digest authentication ...
[Sat Oct 24 21:30:47 2009] [notice] Digest: done
[Sat Oct 24 21:30:48 2009] [notice] Apache/2.2.11 (Unix) DAV/2 PHP/5.2.9 mod_ssl/2.2.11 OpenSSL/0.9.8g mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal operations
[Sat Oct 24 21:30:50 2009] [error] [client 192.168.50.69] (13)Permission denied: exec of '/var/www/cgi-bin/tinyPL.cgi' failed
[Sat Oct 24 21:30:50 2009] [error] [client 192.168.50.69] Premature end of script headers: tinyPL.cgi
Could any one help me on this!
Your log file will have more details regarding the error, but an Internal Server error on a CGI script usually means that when the server tried to execute your CGI program the expected headers was not present.
In a perl script, that would be (for example):
use CGI qw(:standard);
print header();
Which will print out something like:
Content-type: text/html
Try and run your CGI script from the commandline and see if prints out those lines. The other problem might be due to access permissions. Apache might not be able to execute your script.