I have a virtual Machine on VMWare Player: Oracle 11g on Linux Centos.
Since I haven't used it for 2 years, I don't remember almost anything,and when I try to startup the db it says listener is down, and when I try to start listener it says:
TNSLSNR for Linux Version 11.2. 0.1.0 - Production
System Parameter file is /oracle/product/11gR2/network/admin/listener.ora
Log messages written to /oracle/diag/tnslsnr/srvlinux/listener/alert/log.xml
Error listening on: (ADRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
TNS-12542: TNS:address already in use
TNS-12560: TNS:protocol adater error
TNS-00512: Address already in use
Linux Error: 98: Address already in use
What do I have to configure exactly? Thanks in advance.
EDIT:
netstat -tulpn | grep :1521
tcp 0 0 :::1521 :::* LIST
EN 3369/tnslsnr
EDIT:
lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 11-DEC-2012 16:09:54
sqlplus / as sysdba
ERROR:
ORA-12162: TNS:net service name is incorrectly specified
ORA-12162 usually means you don't have ORACLE_SID set - not that it's wrong, but it hasn't been set at all, or has not been exported (depending on your shell). That doesn't tell you anything about whether the database is up, and doesn't imply the listener is down - so don't know if you got a different message from a different connection attempt. Clearly the listener is up on port 1521, from the details you added to the question.
If you're using something Bourne-y (sh, ksh, bash etc.) you need to set and export your ORACLE_SID:
export ORACLE_SID=my_sid
If you can't remember the SID you can go grep -ef | grep ora_pmon_; if that shows anything then the SID is the end of the process name, and the database is up. If it doesn't then look at the output of lsnrctl status and see if anything is registered, or look in $ORACLE_HOME/dbs - files in there might include the SID in their names too.
You might also need to export ORACLE_HOME if you haven't already, but it sounds like you have, probably from your .profile/.bashrc etc.
Related
I am unable to open graphical view of an element in ClearCase.
While doing: clearcase lsvtree -g
I get:
xclearcase : warning: could not load font 'GB2312.1980-0'
Check first (if xclearcase means an old ClearCase 7.x on Linux or Solaris) if this is LANG issue: see this technote.
It was determined that the LANG variable was unset on UNIX® or Linux® and caused the core to occur when the remote display attempted to process xclearcase data.
This could also be caused by an incorrect LANG variable setting.
This may also occur on Red Hat Enterprise Linux (RHEL) 6 when the X11 display is local to the RHEL6 system.
If the LANG environment is set, this issue can be resolved on RHEL5 by changing the LANG environment variable setting from the default en_US.UTF-8 to en_US.
Workarounds:
Option 1:
You may be able to resolve the issue by creating the following link on the server:
/usr/lib/X11/nls/XhpV3/C -> /usr/lib/X11/nls/XhpV3/iso88591
Option 2:
You can try to change your Exceed setting from "PseudoColor" to "Auto Select" in order to connect.
Option 3:
Under BlueZoneX server software, the fix was to tell it to use the Microsoft fonts as well as the ones from BlueZone.
Since my comment gets folded in, I'll enter it as an "answer."
ClearCase explicitly does not support X sessions where the X server is a Windows host. This isn't to say it doesn't mostly work, but when it breaks down, the answer is usually "You're on your own."
http://www-01.ibm.com/support/docview.wss?rs=219&context=SSCBN78&q1=linux&uid=swg21128395&loc=en_US&cs=utf-8&lang=en
A local CTE, or a VNC session are better options for accessing the Unix-based resources from windows without installing the full CC client.
Eclipse over X-forwarding may be acutely painful, depending on the location of the CC host and the X server. I tried it over a VPN once, JUST once. VNC was MUCH better.
Someone, who used to work here, configured a linux box to send snmpset/get requests using MIB object names instead of OIDs. snmpget is called in a shell with some familiar switches and then, bam, just the object name. How is he doing this? Is there a way to configure snmp in linux so that you can do this? I am hearing from coworkers that perhaps there is a way to configure netsnmp on your machine to do the conversion from object names to OIDs.
So we figured this out. In Linux, snmp can be installed on the command line with sudo apt-get install snmp. The syntax is the same as net-snmp. With a basic installation, you have to pas OIDs (which are period separated strings of integers) into snmpget/set to get a response. However, you can see here everything you need to set up your machine to take in the object names. You need to add your mib files to a directory and then point snmp.conf to your mibs.
We've just updated Nagios from 3.5.x to the current version (4.0.7) and subsequently added a new host for monitoring.
The new host shows as 'Down' in Nagios, and this seems to be related to the fact that pnp4nagios is not logging performance data (the individual checks for users, http etc are all find).
Initially there was an error that the directory
/usr/local/pnp4nagios/var/perfdata/newhost.com
that contains the xml setup and rrd files for the new host was missing), so I manually created this directory, but now it complains that the files are missing.
Does anyone know the appropriate steps to overcome this issue?
Thanks,
Toby
PS I'd tag this 'pnp4nagios', but that tag doesn't exist and I can't create them
UPDATE
It's possible that pnp4nagios is a red herring/symptom. Looking more closely I realise that Nagios actually believes the host is down, even though all services are up. The host status information is '(Host check timed out after 30.01 seconds)'...does this make any more sense?
It's indeed very unlikely that pnp4nagios has something to do with your host being down. pnp actually exports output and performance data to feed the rrd database and xml files (via npcd module or evenhandler command).
The fact that nagios reports the host check timed out after 30 sec means that :
- you have a problem with your host check command, please double-check the syntax
- this check command times out after a certain timelapse (most likely defined in nagios.conf) because the plugin was still running.
I'd recommend running this command from the server's prompt. You want to do something like :
/path/to/libexec/check_command -H ipaddress -args
For example:
/usr/local/libexec/nagios/check_ping -H 192.168.1.1 -w 200,40% -c 500,80% -timeout 120
See if something might be hanging. Having the output would be helpful.
Once your host check returns correct output and performance data to nagios, pnp will hopefuly do the rest.
In the unlikely event it helps anyone, pnp4nagios was indeed a red herring. The problem was that ping wasn't enabled for the host being checked, and this is the test for whether a host is up or not. Hence this was failing, despite other services being reported as working.
I cross-compiled NET-SNMP 5.7.1 from sources to a PowerPC using ELDK-3.1.
When I try to load the snmpd daemon in my embedded board, I see the message:
# snmpd -f -Lo
pcilib: Cannot open /proc/bus/pci
pcilib: Cannot find any working access method.
Of course my PPC board has no PCI, and I wonder why is netsnmp looking for it.
In more than one place I see this same message (sourceforge, mail-archive, google-groups), but ir has no answer at all. Another variant, with a little but unhelpful responses at (archlinuxarm).
Can anybody please help me?
I'm assuming you're on a Linux target.
Net-SNMP's changelog lists "[PATCH 3057093]: allow linux to use libpci for creating useful ifDescr strings".
The configure script will search for an available libpci, and, having found one, will define
HAVE_PCI_LOOKUP_NAME and HAVE_PCI_PCI_H. To disable this code: after configuring, you can change those defines in include/net-snmp/net-snmp-config.h, then rebuild. The affected code is in agent/mibgroup/if-mib/data_access/interface_linux.c.
There's also a patch in this bug report: http://sourceforge.net/p/net-snmp/bugs/2449/
I resolved the issue using the stock snmpd that comes with the Raspbian.
In /etc/snmp/snmpd.conf file I isolated the issue to the following line
agentAddress udp:161,udp6:[::1]:161
Instead of listening on all interfaces, if I specify the the ip address of the eth0 interface i.e.:
agentAddress udp:10.0.1.5:161,udp6:[::1]:161
Then snmpd starts fine.
My speculation is that the stock snmpd tries to enumerate all possible interfaces including the pci ones.
I've got the following settings in my postgres conf:
log_destination = 'stderr'
redirect_stderr = on
log_directory = '/tmp/psqlog'
log_statement = 'all'
And yet no logs are logged. What am I missing here? There is reference on the internet to a variable called "logging_collector", but when I try and set that, postgres dies on startup with a FATAL: unknown variable.
This is on MacOS 10.4.
Ta.
I believe that you need to change log_destination to "syslog" or a specific directory. Output that goes to stderr will just get tossed out. Here's the link to the doc page, but I'll see if I can find an example postgresql.conf somewhere http://www.postgresql.org/docs/8.2/static/runtime-config-logging.html
This mailing list entry provides some info on setting up logging with syslog http://archives.postgresql.org/pgsql-admin/2004-03/msg00381.php
Also, if you're building postgres from source, you might have better luck using a os x package from Fink or MacPorts. Doing all of the configuration yourself can be tricky for beginners, but the packages normally give you a good base to work from.