Text spat out when running gedit as root

After upgrading to gnome 2.24, terminal has spat out more junk when opening gedit as root.
It does open it, it just print these lines.
Before it was a few lines, now it is this:
[duncan@duncan-arch ~]$ su
Password:
bash-3.2# gedit /etc/pacman.conf
(gedit:19944): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Last edited by Raccoon1400 (2008-10-28 10:36:39)

Onyros wrote:
Hi there, it's a known bug since Gconf's upgrade from 2.22 to 2.24, it's filed in Gnome's bugzilla and also in Arch's bug reporting system, here. A solid workaround for now is using sudo instead of su, and I expect it to be solved... soon.
Another not so solid workaround is downgrading to Gconf 2.22 (someone made it available in that bug report, and downgrading does work).
Some people have even had problems with other related stuff, like shutting down/suspending/hibernating. A collateral effect is the greying out of preferences in apps like Gedit, etc.
This doesn't look like the same issue. Am I missing something?

Similar Messages

Installing Clusterware/ASM Grid 11.2.0.1, errored out when running root.sh

Working through the installation of Clusterware/ASM Grid using 11.2.0.1.
After running the first root.sh script, no problems. On the second one, getting this error:
Adding daemon to inittab
CRS-4124: Oracle High Availability Services startup failed.
CRS-4000: Command Start failed, or completed with errors.
ohasd failed to start: Inappropriate ioctl for device
ohasd failed to start: Inappropriate ioctl for device at /u01/app/grid/1120/grid/crs/install/roothas.pl line 413.
Any ideas of how to get this running?

Hi guys,
I'm having this problem on the second node and in the /var/log files I'm getting these errors.
Can any one help?
Regards,
Ahmed
May 26 16:05:37 node su(pam_unix)[7567]: session closed for user oracle
May 26 16:05:37 node logger: Failure in CSS initialization opening OCR.
May 26 16:05:37 node su(pam_unix)[7571]: session closed for user oracle
May 26 16:05:37 node logger: Failure in CSS initialization opening OCR.
May 26 16:05:37 node su(pam_unix)[7570]: session closed for user oracle
May 26 16:05:37 node logger: Failure in CSS initialization opening OCR.
May 26 16:05:37 node su(pam_unix)[7583]: session closed for user oracle
May 26 16:05:37 node logger: Failure in CSS initialization opening OCR.

System is showing time out when run in background

Dear all,
We have two systems: One R/3 and EBP. We have made one report where the remote function module will be called from R/3 to EBP. There are 4 lakhs data in SAP. We are sending 10000 data as package in internal table and getting the corresponding output. But the system is showing time out when the report has run in background. Can you please suggest how the process can be improved so that the timeout can be avoided.
Thanks and regards,
Atanu

Hi,
Try to fetch records in smaller chunks and process them. For example, if you are trying to fetch records for one year, instead of single query, try to fetch in 12 sets for each month. Fetch first month and process the records and put them in the output internal table. Then go for next month and so on. Anyway your program is running in background. There will not be any user complaint also. The solution might sound bit funny. But it works.
Regards,
Hema

Connection timed out when running snpsftp (Odisftp) jython procedure

Hi All,
Let me know the solution if any one of you have come across the "Connection Timed Out" error when running a jython snpsftp (Odisftp) procedure to exchange/import the files on a FTP server to the local system (Target Server).
This procedure was working fine until the IP Address of the Target Server was changed due to change to physical location of the Target server itself.
Since we are moving office to a different building the Target server which hosts the ODI Agent running as windows service are moved and since then the FTP Jython procedure is not working.
I can successfully ping the IP Address of the FTP server from the Target server that has got the new IP, but when running the FTP procedure from ODI tool ends up with Connection Timed Out error.
Thanks for providing some tips/ideas for resolving this urgent issue.
Thanks,
Raghu

Please check the hosts file for the new IP,
Also cehck the Agnet service login for wheter the user has the privledges to do a FTP access to the server or also connect to the server
Reshma

The number of rows per page is greyed out when running in background?

Hi,
For a customized transaction the number of rows per page cannot be set when running in background.
While a background job is created in SM36 after entering the report name and the selection variant name in the properties of Format the rows and columns field is greyed out.It was not editable.
Is there any settings to be done or in the custom program any code change needs to be done?
Thanks in advance.
Regards,
Sharon.

Hi Gabriel,
After double clicking the format only the rows field is not set to edit.It was greyed out.Is it anything related to the printer settings that will be maintained for a user?
Regards,
Sharon.

10g CRS: ocrconfig hangs when running it from root.sh during installation

Hi,
we are trying to install a RAC 10g on Suse Linux 9.1 using raw files on shared SCSI disks. We told the system to be a supported red hat distribution (the way described elsewehere in OTN), linked compress to gzip and gave the oracle user writing access to /dev/raw/raw1, the ocr partition Installation went fine until the root.sh execution.
ocrconfig did not return when called from the root.sh
>>>
# GSD should be down when this script is called.
# 1. Calls ocrconfig -migrate to migrate Oracle Cluster Registry contents from 9.2 to 10i format.
if $CH/bin/ocrconfig -upgrade $ORACLE_OWNER oinstall;
then
$ECHO "Oracle Cluster Registry configuration upgraded successfully"
else
$ECHO "Failed to upgrade Oracle Cluster Registry configuration"
exit 1
fi
<<<
the ocrconfig log shows
>>>
05/04/2004 10:58:36
ocrconfig starts...
Warning!! cluster checking is disabled
Upgrading OCR data
<<<
has anyone an idea, what the problem is?
Matthias

What did you do to solve this problem, i have same problem az you. whenever i execute root.sh it stops at line 743 and shows me:
Failed to upgrade Oracle Cluster Registry configuration
this is my whole output result of root.sh script.
Running Oracle10 root.sh script...
\nThe following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/crs/oracle/product/10.1.0/crs
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
Checking to see if Oracle CRS stack is already up...
/u01/crs/oracle/product/10.1.0/crs/root.sh: line 573: 6527 Segmentation fault $CH/bin/crs_stat >/dev/null 2>&1
Setting the permissions on OCR backup directory
free(): invalid pointer 0x80cdc48!
/u01/crs/oracle/product/10.1.0/crs/root.sh: line 743: 6554 Segmentation fault $CH/bin/ocrconfig -upgrade $ORACLE_OWNER $CRS_DBA_GROUP
Failed to upgrade Oracle Cluster Registry configuration
any help appreciated.
hasan

[SOLVED]Home directory confusion when running Emacs as root

Hi, just set up my first Arch system. I've installed emacs-nox, and it insists on using the .emacs file of the one normal user I have set up, even when I'm not logged in as that user. Bits in that .emacs file which use a tilde to signify $HOME do point to /root when I'm logged in as root, causing various weirdnesses.
Here's what --debug-init says when I run emacs as root; if there's anything apart from the complaint about the "missing" (not in /root) haskell-mode files, I'm afraid it means nothing to me
edit: nope, all of that junk really was about the haskell-mode stuff, so I'm deleting it since that's "fixed" by copying that stuff to /root/.emacs.d. Now --debug-init tells me nothing and I still have no idea why emacs insists on using the dotfile in /home/j
Last edited by cuns (2011-12-25 23:21:06)

I have this issue, too if starting emacs after doing a "su" - when logging in as root it works as expecte. Googling brought the emacs changelog:
1987-05-12 Richard M. Stallman (rms at prep)
* startup.el (command-line): If running under `su',
use user's original login name to get init file.
Otherwise use $HOME.
A workaround would be to define an alias like
alias emacs='emacs -u root'
in your root's ".bashrc" (/root/.bashrc).
Hope that helps,
greetings
matse

9iAS rel 2 SLOW and report times out when running !! HELP !

Hello,
I have 9iAS installed on Win 2K machine SP 2.
I have done the BI install with the infrastructure in a separate home.
I have 524K RAM.
EM is VERY SLOW (as per usual).
I have rebooted the server a few times - still slow.
When I try to run a report it times out just bringing up the parameter page !
If I try to kill the report I run into BUG 2544383 which is a fat lot of use ....
This 9iAS is absolute garbage - how can Oracle tell us to migrate our existing developer forms & reports to web-deployment from client server if this sort of performance is going on ? This is still in development - if this was a production machine this would be TOTALLY UNACCEPTABLE !!!!!
Does anyone from Oracle actually respond to these threads or are they too busy writing bugs for the next release of 9iAS ?
Seriously though, if anyone has some workarounds for these issues then please let me know.
Thanks

We got aound the ADMN error by manually starting the components that were down in Infrastructure first then the ones in the BI instance all thru EM.
FYI Oracle said this to me about recommended h/w :
The Installation Guide for iAS sets the minimum requirements for installing iAS as:
Infrastructure 512Mb RAM
Mid Tier install with 4 or more components 512 Mb RAM
Please remember that these are minimums only and are not the recommendations for anything larger than a small workgroup installation. The main points to remember are to install the OS on a seperate physical disk from the Applications and to have as much RAM as you can beyond the minumums. But even this approach has its limitations and so you may then have to consider different approachs to maximising scalablility. It is also not recommended to have the Infrastructure and Mid-tier installed on the same machine for larger systems as you are more likely to encounter resource limitations due to the different installations serving different purposes.
So we are going to go with your minimum 2 Gig with 7 gig swap file I think.
I think we may go for a 3-server setup.
one with Infrastructure and Portal on it.
The other 2 with BI installs on them with them probably running in some sort of cluster (either hardware or software cluster). All with 2 gig RAM.
I still don't know why somtimes my reports hang - I think it may possibly be BUG 2544383 which to me is a major issue as a lot of our reports are PDF as users print them out. But essentially it screws up the AS and invariably I have to either restart the WHOLE instance or reboot the server ! NOT very good for when I want to go Live with this !

Memory maxed out when running weblogic 4.5

I am the tech support guy for my office, but I am WebLogic illiterate. I have a user who is running WebLogic, but when he runs it, his RAM and virtual memory max out. Are there any settings in WebLogic for memory allocation? Or is there a known problem with memory?

Please see my reply in misc.
Michael Girdley
Product Manager, WebLogic Server
BEA Systems Inc.
Jay A. Fulks <[email protected]> wrote in message
news:89gt0e$91a$[email protected]..
Hi.
I am running WebLogic 4.5.1.5 under Solaris 2.6. I am using JDK 1.2.2
with HotSpot. When we shutdown our server, it essentially crashes with
the following error:
# HotSpot Virtual Machine Error, Unexpected Signal 11
# Error happened during: mark sweep
# Error ID: 4F533F534F4C415249530E4350500BC2 01
After looking into the problem, we found that it is easily recreatable,
simply
by (1) starting the server, (2) hitting any web page (which causes
FileServlet
to be loaded), and (3) shutting down the server.
I have attached a tail of my log file as evidence.
Anybody else seen this problem? Is it a Weblogic/HotSpot compatibility
problem?
Thanks.

Need Recommendation for Ear Piece that Won't Fall Out When Running

I've got a nano with the Nike sensor and jog nearly every day. It drives me crazy that the ear pieces that came with the nano fall out several times during my run. Can someone recommend a good set that will not fall out and sounds good? Not to sound like an a@@, but price is no object. In other words, what are the best possible ear phones that I can buy to jog with?

Well, if you can find a pair of in the ear canal earphones that fit you well (I had to try a couple of different brands), they might work for you. I like etymotic research er-6is. I find that when I take the trouble to seat them properly, they stay in no matter what. The only irritating thing about them is I can hear the cord moving.
I've also used a cheap pair of Koss earphones that have a plastic piece on each one that goes around the ear. The sound was adequate. However, when I'm running on the street, I don't mind the less than stellar quality and I can hear what's around me. I think Sony makes a well regarded set of earphones that with similar over the ear pieces. I don't remember the model number.

Time out when run execute report on Webgui or transaction iView

Dear All,
We found the error as bellow when we execute report that load huge size of data so it would like many time to get it.
500 Connection timed out
Error: -5
Version: 7000
Component: ICM
Date/Time: Thu Mar 6 19:33:49 2008
Module: icxxthr_mt.c
Line: 2698
Server: irpc16_QAS_50
Error Tag: {-}
Detail: Connection to partner timed out after 60s
Anyone please tell us about the way to edit timeout of webgui or iView.
Thank you very much,
Anek.

Dear Krishna
It's helpful.
Goto rz10 transcation
Choose: Instance profile
Select: extended maintaince
Click: change
Set value for parameter 'icm/keep_alive_timeout'
If there is not parameter 'icm/keep_alive_timeout', create it.
Save it.
Restart SAP.
Please tell me how to give point for you.
Thank you for ur reply,
Anek.

Crystal Report Viewer error out when running multiple instances

Hi,
I am using java 1.4 with BO XI R3.0.
I notice I can only run one report at a time. If I was to run two reports, the 1st report will error out while 2nd report will run to its completion. Reports run on separate popup windows. I have tested with IE6, IE8 and also FireFox 3.0
Depending on the timing, I get different kinds of error.
"A request was cancelled. The necessary security privileges could not be verified. This indicates a problem with the security server. [RCIRAS9190] [RASLIB9002] "
"The Report Processing Server session you are using to connect is in the process of being shut down. You need to retry. [RCIRAS0200]"
I am using PSReportFactory and set parameters into CrystalReportViewer to display.
processParametersu2026
CrystalReportViewer viewer = new CrystalReportViewer();
pfieldDV = new ParameterFieldDiscreteValue();
pfieldDV.setValue(formatViewerParameterInputValue(tempRpt[1],tempParam[x]));
pfield.getCurrentValues().add(pfieldDV);
viewerParameters.add(pfield);
viewer.setParameterFields(viewerParameters);
createCrystalViewer(m_oReportWrap.getRequest(), response, sInstanceId,viewer);
private void createCrystalViewer(HttpServletRequest request, HttpServletResponse response2, String sInstanceId, CrystalReportViewer viewer) throws ReportSDKExceptionBase, FileNotFoundException, IOException, SDKException
         IEnterpriseSession eSession = oLogon.getCESession();
         IInfoStore iStore = oLogon.getInfostore();
         IInfoObject rptObject = findInfoObject(iStore,sInstanceId);
         IReportSourceFactory rptFactory =    IReportSourceFactory)eSession.getService("","PSReportFactory");
         IReportSource reportSource = rptFactory.openReportSource(rptObject,Locale.ENGLISH);
         IReport report = (IReport)rptObject;
        ConnectionInfo conn = new ConnectionInfo();
        ConnectionInfos connInfo = new ConnectionInfos();
        ServletContext sc = getServletConfig().getServletContext();
        String realPath = sc.getRealPath("");
        Properties prop = new Properties();
        viewer.setOwnPage(true);
        viewer.setDatabaseLogonInfos(connInfo);
        viewer.setReportSource(reportSource);
        viewer.setURI(request.getRequestURI() + "?reportID=" + rptObject.getID() + &viewerType=vwrTypeJavaSDK&viewID=1");
        viewer.setEnterpriseLogon(eSession);
        viewer.setHyperLink("New Window");
        viewer.processHttpRequest(request, response2, sc, null);

Thanks to both of you.
I actually was able to resolved this issue by tracking the values inside IEnterpriseSession.
// Perform Crystal Enterprise Logon
ISessionMgr oSessionMgr = CrystalEnterprise.getSessionMgr();
IEnterpriseSession m_oCESession = oSessionMgr.logon(sUserid, sPassword, sSystemName, getSecTypeString(iSecType));
System.out.println("in logon m_oCESession "+m_oCESession);
The UserInfo in the SeucuritySession: userInfo was always null so whatever i pass in, it was not storing them.
(EnterpriseSession:logon=(SecuritySession:userInfo=null)
All i need to do is to add   IUserInfo userInfo = null; before IEnterpriseSession then it will store the user & password.

Why is text washed-out when I'm using a color-filled text box?

I have created some text boxes in InDesign. I've colored them a lighht green, and I am trying to type into them but my text is washed out, even though I am picking a much darker text than the box fill. How do I fix this? I am working on a tight deadline! Please help.

Thanks. Here's a screenshot. I'm referring to the light green boxes on the side. The text I'm using is the same color as the text above that says "appalachian ohio" but it isn't showing up.

Setup is timing out when running install for M175 on Win XP Pro

This is a new problem that has come up since I changed my WEP code on my WiFi and am now trying to edit it for my printer to continue operating wirelessly. theis setup has been working for almost three years.
I've tried running setup (4.0.2.6223) with USB or Wireless configuration and in every case it times out (Fatal Error: An install operation took too long to...). I've reviewed the HP blogs and tried many of the solutions with no luck. I am logged in as administrator and have changed spooling to manual in services. I have tried to turn off all services and hide the MS stuff in msconfig but I get an access error. I also believe that Universal Printing services is on but don't know where to disable it.
I have done tech for the last 25 years and have had literally hundreds of HP products. This proble has brought me to my knees.
I hope you can help
Thanks
Ron Joyal

Thanks for letting me know that information RonJoyal. Sorry to hear that you are still unable to install the software, you are also having the same issue with a second computer.
I believe with the USB install the Universal driver is the default driver being installed which is causing this issue.
Please follow the steps provided below:
Remove the drivers first from the Print Server Properties. How to Locate Print Server Properties for Windows 7. On the Driver tab, highlight and remove the printer. Remove the Laserjet and any Universal drivers.
Run the uninstall again to remove all the files that previously installed.
Run the install again. After connecting the USB, immediately follow this document please, to update the driver. The driver is probably defaulting to the Universal driver which is causing the software to time out. Then the install should continue through. A Fatal Error Displays During Software Installation.
Are you doing this installation remotely?
If you are still running into issues, then connect the Ethernet cable from the printer to the router, temporarily.
Run the install to see if the drivers will fully install by this connection.
Follow these steps to configure the wireless now.
Wait about a minute, print the configuration page to see if you get a IP address.
Printing a Configuration Report.
Then type the IP address into Internet Explorer's address bar to bring up the printer's web page. Select the networking tab, wireless on the left hand side. Fill out all your network information, select infrastructure, select your network name, put in password and type of encryption. Apply settings.
Then disconnect the Ethernet cable.
Wait for few minutes and you should get a wireless light on the printer, print the configuration page and check the IP address again. Then type the IP address into Internet Explorer's address bar to bring up the printer's web page. Just to make sure it is still on the network.
Then flip the port with the new IP address.
Go to start, devices and printers, right click the printer and left click printer properties, select the ports tab.
Click Add Port, select Standard TCP/IP Port, then select New Port and follow the wizard.
Type in the proper IP address for the printer.
Make sure the printer is online.
Test the printer.
Let me know the results.
Thank You.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Gemini02
I work on behalf of HP

Not displaying customized themes when running apps as root

The thing is that i usually have compiz enabled as normal user... but whenever i run an application as root, this appears withouth any decoration........ i know is really not really important thing,but the point is that i remember it not happening before..... which could be the reason for this behaviour?
thanks!

Xi0N wrote:
The thing is that i usually have compiz enabled as normal user... but whenever i run an application as root, this appears withouth any decoration........ i know is really not really important thing,but the point is that i remember it not happening before..... which could be the reason for this behaviour?
thanks!
like ronin said you would have to set up your themes for root, It's good they look different though then you won't forget they're running as root and do something you shouldn't thinking the app is running as a user.

Text spat out when running gedit as root

Similar Messages

Maybe you are looking for