Debugging avahi

I've recently upgraded from opensolaris b134 to solaris 11 express.
In the upgrade process I had to remove a lot of old third party stuff to bring me back to a clean system, this caused me to need to rebuild a new netatalk (I grabbed the latest version). I've installed it in /opt/netatalk to keep unpackaged stuff separate.
Now netatalk isnt the issue, I can ALWAYS get to my shares by using finder and Go->Connect to Server
Normally when I open my mac, the solaris machine shows up in the left finder bar, Time Machine sees it and can happily back up to it. After my mac has been on for say half an hour (I'm not sure exactly the timing, but a little while) the solaris machine drops off the finder bar. Time machine isnt happy as it then cant mount its backup volume, however if I use finder to manually connect via afp it works. This leads me to believe this is an avahi issue on the solaris machine, or an issue on the mac (which funnily enough got a system update around the same time).
How does this all work? what causes broadcasts? does the solaris box simply answer requests, or does it periodically announce, or it responds to the laptop announce by announcing itself? I'd like to figure out what keeps the solaris machine in the finder, and then hopefully figure out why that isnt happening (solaris avahi issue, osx bug, network bug, configuration etc).

*bump*
any ideas?

Similar Messages

Avahi-daemon doesn't start, no "ck_daemon"

Hello. Two weeks ago or so I realized during boot that Avahi daemon fails to start. Now I've debugged it and it seems like it's start sequence attempts to use "ck_daemon" command, which is not available. How can I obtain this executable or substitute it?
Last edited by Thar (2012-01-25 14:48:44)

What are the contents of 'cat /etc/rc.d/functions' and 'cat /etc/rc.d/avahi-daemon'? (Use [ code ] blocks)
'ck_daemon' is a function defined within '/etc/rc.d/functions' which should be sourced as part of the daemon script.

Kdelibs with avahi

I have modified the kdelibs PKGBUILD from abs to use avahi instead of mdnsresponder, it anyone wants it.
Just place this in the abs dir for kdelibs:
# $Id: PKGBUILD,v 1.53 2006/01/27 15:56:49 tpowa Exp $
# Contributor: Roman Kreisel <[email protected]>
# Maintainer: Tobias Powalowski <[email protected]>
pkgname=kdelibs-avahi
pkgver=3.5.1
kdever=3.5.1
pkgrel=1
pkgdesc="KDE Core Libraries"
url="http://www.kde.org"
groups=('kde')
depends=('arts>=1.5.1' 'db' 'libxslt' 'pcre' 'libart-lgpl' 'openexr' 'avahi' 'jasper'
'fam' 'bzip2' 'openssl' 'libidn' 'perl' 'aspell' 'heimdal' 'acl' 'libtiff' 'qt>=3.3.5')
makedepends=('cups')
provides=('kdelibs')
conflicts=('kdelibs')
# for easier build, just uncomment the mirror you want to use
mirror="ftp.solnet.ch/mirror/KDE" # updated every 2 hours, very fast for Europe
# mirror="ftp.kde.org/pub/kde/" # main server
# mirror="ibiblio.org/pub/mirrors/kde/" # ibiblio mirror
source=(ftp://$mirror/stable/$kdever/src/kdelibs-$pkgver.tar.bz2
applications.menu.patch kdeprintrc.patch fileshareset-wrapper.c kde-menu.patch xdg-icon-lookup.patch
html_misc.patch
http://helios.et.put.poznan.pl/~jstachow/pub/kdnssd-avahi_0.1.2.orig.tar.gz)
build() {
# Source the QT and KDE profile
[ "$QTDIR" = "" ] && source /etc/profile.d/qt.sh
[ "$KDEDIR" = "" ] && source /etc/profile.d/kde.sh
# start building
cd $startdir/src/kdelibs-$pkgver
patch -Np1 -i $startdir/src/kde-menu.patch || return 1
patch -Np0 -i $startdir/src/xdg-icon-lookup.patch || return 1
patch -Np0 -i $startdir/src/applications.menu.patch || return 1
# fix for kdebindings
patch -Np4 -i ../html_misc.patch || return 1
#automake
./configure --prefix=/opt/kde --with-distribution="Arch Linux" --with-alsa
--disable-dependency-tracking --disable-debug
--enable-dnotify --enable-sendfile --without-hspell
--enable-gcc-hidden-visibility --enable-final --disable-dnssd
# --enable-final # remove this if you build with < 512mb ram.
make || return 1
make DESTDIR=$startdir/pkg install || return 1
# Hack-ish way to get Avahi support
cd $startdir/src/kdnssd-avahi-0.1.2
./configure --prefix=/opt/kde
cd kdnssd-avahi && make mocs && make
cd ../
make || return 1
make DESTDIR=$startdir/pkg install
# Set cups as default printing system
cd $startdir/pkg/opt/kde/share/config
patch -Np0 -i $startdir/src/kdeprintrc.patch || return 1
# fix that stupid fileshareset suid problem
mv $startdir/pkg/opt/kde/bin/fileshareset $startdir/pkg/opt/kde/bin/fileshareset.pl
gcc -Wall $startdir/src/fileshareset-wrapper.c -o $startdir/pkg/opt/kde/bin/fileshareset
chmod 0755 $startdir/pkg/opt/kde/bin/fileshareset.pl
chmod 4755 $startdir/pkg/opt/kde/bin/fileshareset
rm $startdir/pkg/opt/kde/bin/filesharelist
cd $startdir/pkg/opt/kde/bin/
ln -s fileshareset.pl filesharelist
md5sums=('2a22193ae7c23f3759b02723dab02d30' 'a66270abcdd0dcb2e28d3b2464927ff6'
'6061c259247f56f0ede21deabfad2732' '60ab1a486895d6c18ef334ec958c48d6'
'e94aef45b5a59fe58c7cc085ab1dd3ae' '3627a48526fefa2fe2beeff43f35ac0f'
'ac1421ba31fe20e8108b5ffb509b11b0' '36e7073d39d692c9f45b22c1044eb563')

Well, I got one report claiming this as a success, you just need avahi started before getting into kde or else kicker will go bonkers

CUPS not printing to network printer.Printer visible to avahi and cups

Hey. Printing seemed to be working fine last time I checked (which, granted, was a while ago...I don't print that much). I have a networked Canon MG4100 class printer. Avahi sees the printer just fine, as does cups (I can add and modify the printer without any troubles). However when I try to print, it starts printing but then the Cups interface notifies me 'Unable to locate printer "canon.local".'
1. The printer works fine from a windows laptop
2. I reset the printer and the wireless router it's attached to
3. I restarted my laptop
4. Here are the /var/log/cups/error_log (debug level) logs
5. /etc/cups/cupd.conf
6.
10:06:50 $ avahi-browse -atl
+ wlan0 IPv4 Canon MG4100 series Web Site local
+ wlan0 IPv4 Canon MG4100 series _scanner._tcp local
+ wlan0 IPv4 Canon MG4100 series UNIX Printer local
+ wlan0 IPv4 Canon MG4100 series _canon-bjnp1._tcp local
7. journalctl -b -u cups
-- Logs begin at Mon, 2012-10-22 06:49:03 PDT, end at Mon, 2012-10-22 06:49:37 PDT. --
Nov 08 09:30:31 scotty cupsd[9321]: Unknown directive DefaultAuthType on line 9.
Nov 08 09:32:47 scotty cupsd[9321]: process 9321: arguments to dbus_connection_close() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file dbus-connection.c line 2890.
Nov 08 09:32:47 scotty cupsd[9321]: This is normally a bug in some application using the D-Bus library.
Nov 08 09:32:47 scotty cupsd[9321]: D-Bus not built with -rdynamic so unable to print a backtrace
Nov 08 09:33:15 scotty cupsd[16183]: Unknown directive DefaultAuthType on line 8.
Nov 08 09:44:27 scotty cupsd[8469]: Unknown directive DefaultAuthType on line 8.
Nov 08 09:52:01 scotty cupsd[30618]: Unknown directive DefaultAuthType on line 8.
Nov 08 09:55:15 scotty cupsd[6143]: Unknown directive DefaultAuthType on line 8.
8. Oh, and I tried downgrading cups and cups-filters to the previous versions from the beginning of September. Same issue.
What the heck am I missing???
Thanks!
Scott

I'll look into that when I get a chance. I'm just using the Gutenprint drivers. They were working fine up until recently...I just don't know at what point because I rarely print! I'm a little leery of adding the printer with a static IP address, because it's not a static IP setup...I know it should stay the same for the most part, but I thought that's why we used Avahi...to get away from having to know the IP address!
Thanks for the input!
Scott

[SOLVED]Couldn't open file for 'Log debug file /var/log/tor/debug.log'

Hello,
I'm trying to run a tor relay on my arch linux box. Trying to launch the tor daemon, here's the log via
$ systemctl status tor.service
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.877 [notice] Tor v0.2.4.21 (git-505962724c05445f) running on Linux with Libevent 2.0.21-stable and OpenSSL 1.0.1g.
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.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
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.877 [notice] Read configuration file "/etc/tor/torrc".
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.909 [notice] Opening Socks listener on 127.0.0.1:9050
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.909 [notice] Opening OR listener on 0.0.0.0:9798
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [warn] Couldn't open file for 'Log debug file /var/log/tor/debug.log': Permission denied
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9050
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [notice] Closing partially-constructed OR listener on 0.0.0.0:9798
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [warn] Failed to parse/validate config: Failed to init Log options. See logs for details.
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [err] Reading config failed--see warnings above.
May 20 11:53:10 arch systemd[1]: tor.service: main process exited, code=exited, status=255/n/a
May 20 11:53:10 arch systemd[1]: Unit tor.service entered failed state.
Why the tor daemon cannot write into /var/log/tor/debug.log ?
Here's my /etc/group
root:x:0:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin
adm:x:4:root,daemon,nue
tty:x:5:
disk:x:6:root
lp:x:7:daemon
mem:x:8:
kmem:x:9:
wheel:x:10:root,nue
ftp:x:11:
mail:x:12:
uucp:x:14:
log:x:19:root
utmp:x:20:
locate:x:21:
rfkill:x:24:
smmsp:x:25:
http:x:33:
games:x:50:
lock:x:54:
uuidd:x:68:
dbus:x:81:
network:x:90:
video:x:91:
audio:x:92:
optical:x:93:
floppy:x:94:
storage:x:95:
scanner:x:96:
power:x:98:
nobody:x:99:
users:x:100:
systemd-journal:x:190:
nue:x:1000:
avahi:x:84:
lxdm:x:121:
polkitd:x:102:
git:x:999:
transmission:x:169:
vboxusers:x:108:
tor:x:43:
mysql:x:89:
Last edited by giuscri (2014-05-20 12:18:56)

SidK wrote:You must have modified your torrc to print to that log file. systemd starts the service as the tor user (see /usr/lib/systemd/system/tor.service). So if if you want to log to a file the tor user must have write access to it. By default however tor it set to log to the journal, which doesn't require any special permissions.
Yes. I did edit the torrc file since I wanted the log to be store in that file. Indeed
## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log
## Send every possible message to /var/log/tor/debug.log
Log debug file /var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
Log notice syslog
## To send all messages to stderr:
#Log debug stderr
I missed the file systemd uses to choose who's the process owner.
Course, I could edit /usr/lib/systemd/system/tor.service such that root will become the process owner; or, I could add the user I use everyday in the root group, then change the permission of /var/log/tor/debug.log such that it will be writable also for the folks in the root group.
Yet they both seems to be a bit unsafe ...
What is the best choice, to you guys?
Thanks,

Debugging is not working in R/3 from WebDynpro-ABAP developed webpage input

Dear Friends,
We are facing a serious problem for debugging. Expecting valuable input for the same.
Debugging is not working in R/3 from WebDynpro-ABAP developed webpage input in Production Server.
The debugging (for WebDynpro-ABAP application) is working in Dev. Server for
1st ] Within R/3
Ex. debug for bapi within R/3. i.e. value enter as input in R/3 only.
2nd ] From webpage to R/3
Ex. Some input given on the internet web page developed through WebDynpro and external breakpoint set in R/3 it works. It directs to R/3 code through debugging.
In Prod. Server the 1st case above is working but the 2nd case is not working.
In Prod. Server the WebDynpro developed applications are running successfully through internet explorer webpage inputs. So running the application is not a problem in prod. Server but debugging of the same is the problem.
The setting which are done in Prod. server are,
1] RZ10 in parameters are set for port and host name.
2.1] In SMICM check for ICM.
2.2] Host file updated in Windows-System 32.
3] In SICF following services are active,
3.1] default_host/sap/bc/webdynpro
3.2] default_host/sap/public/bc
3.3] default_host/sap/public/bc/webdynpro/viewdesigner
3.4] default_host/sap/bc/wdvd
3.5] default_host/sap/public/icman
3.6] default_host/sap/bc/gui/sap/its/webgui
3.7] default_host/sap/public/ping
3.8] default_host/sap/bc/error
3.9] default_host/sap/bc/echo
4] In SE80
4.1] Internet services-System-are published
4.2] Internet services-WEBGUI-are published
4.3] Utilities-Setting-ABAP Editor-Debugging-Username & New Debugger set.
4.4] Utilities-Setting-ABAP Editor-Editor-Front-End Editor(New) set.
5] In Su01 for user profiles sap_all & sap_new is assigned and role SAP_BC_WEBSERVICE_DEBUGGER is assigned.
6] The support packages are also updated to latest level.
7] Gone through following links but not getting any clues.
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/74d50bd1431b5ae10000000a42189c/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/EN/77/3545415ea6f523e10000000a155106/frameset.htm
Thanks in Advance.
Best Regards,
Abhijit.

No cross posting
Read the "Rules of Engagament"
Regards
Juan

Firefox can't open normally without going through the "this is embarrassing" routine; nor does it close down properly; it also sticks frequently, i.e. screen freezes for a minute or more; should I uninstall and re-install to try and debug?

Firefox can't open normally without going through the "this is embarrassing" routine; nor does it close down properly; I get the "end program" message and have to say "end now"it also sticks frequently, i.e. screen freezes for a minute or more; should I uninstall and re-install to try and debug?
- I've used Firefox exclusively for around 2 years.
- My outlook express has no problems
- other programs seem unaffected; it seems peculiar to Firefox.
- my main use is surfing the net, primarily entering competitions on line via specialist competition sites.
- every day at some stage(s) I have to switch computer off as Firefox has got very slow/sticky/freezes.
I'm not techy by any means, but I can only thing of un- and re-installing to hopefully start with a clean slate.

Sounds like something is keeping Firefox from closing properly. See this: <br />
https://support.mozilla.com/en-US/kb/Firefox+hangs#Hang_at_exit

ERROR while debugging a SELECT..ENDSELECT

Hello All,
We get an error while we go into the select..endselect loop during debugging. Because of this if we try to do some research on existing program with Select-endselect..it fails in the second pass of this loop.
This problem was not there earlier, but after we upgraded from 4.6 to 4.7 this problem is bugging us..every day. Does any one have a clue why ?
Thanks!!
Regards,
Vishal

Hi,
debugging a SELECT...ENDSELECT statements brings to a LUW commit work if no other work processes are available for debug.
See OSS notes 675, 2104.
From OSS note 675 **********************************
Cause and prerequisites
Chain of causes:
      1. There is a statement in one of the Select loops, that leads to a database Commit (or Rollback).
      2. A database Commit causes the database to lose the cursor.
      3. The system cannot automatically continue within Select loop after loss of cursor.
Following statements lead to a database Commit:
    * All statements that cause a change of screen (CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT, I/W-Message)
    * BREAK-POINT/ Debugging
      . if no debug process free
      . always after regeneration (in order to release generation lock).
    * WAIT Here a work process is released and a Commit is executed.
    * COMMIT WORK/ROLLBACK WORK
From OSS note 2104 **********************************
Solution
The "COMMITWORK" message appears in the ABAP debugger when programs
orscreensrequireregeneration,or when not enough free capacity
is available inthesystem (or else the debugger blocks a system
process).
Normallyonly one work process is released for debugging. This
isgenerally insufficient ina developmentsystem, as processes
can be blocked for other reasonstoo(background processing,
CPI-C connections,andso on).
The number of work processes made available for debugging can
be configured using the profileparameter
                  rdisp/wpdbug_max_no
Forexample:
                rdisp/wpdbug_max_no = 10
setsthe maximum number of work processes made available for
debuggingto 10. It may be necessary to generally increase the
numberofwork processesatthis time (parameter rdisp/wp_no_dia).
In all other known cases, an error in the application program is
involved.
Regards, Manuel

DID YOU KNOW?: Debugging with BC4J Tester

Did you know that in JDeveloper 3.2, you can run the BC4J tester in debug mode to exercise your business components and hit breakpoints at the same time?
Just do the following:
[list]
[*]Expand the navigator node for your Application Module, revealing its XML and Java implementation files.
[*]Right-mouse on the YourAppModImpl.java file, and select Debug...
[list]
By default, it will debug using the "local mode" connection configuration. If you want it to debug using a difference configuration, just change the configuration name that appears as the 2nd argument in the launchTester call in the main() method of the application module implementation file.

grin Thanks, Steve.
Does this mean that in JDev 5.0 we're going to see an animated Steven Muench head in a tiny window in the lower corner, occassionally tapping on the glass to offer us hints?

Error when starting Weblogic in debug mode

Hi there
Has anyone experienced any difficulties when starting weblogic in debug mode.
More specifically, it cannot start correctly because it thinks that another instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unable to create
a server socket for port: 8320. java.net.BindException: Address already in use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <The WebLogic
Server is no longer listening for connections. You should probably restart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Server shutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdown sequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Server shutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unable to load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)

Thanks for the suggestion.
Unfortunatley the port is definately free/available during startup.
Stephane Kergozien <[email protected]> wrote:
Maark,
Before starting your server, please could you check that the port is
not used by one
other process. You can use the netstat command to do this.
Regards
Stephane
Mark wrote:
Hi there
Has anyone experienced any difficulties when starting weblogic in debugmode.
More specifically, it cannot start correctly because it thinks thatanother instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unableto create
a server socket for port: 8320. java.net.BindException: Address alreadyin use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <TheWebLogic
Server is no longer listening for connections. You should probablyrestart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Servershutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdownsequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Servershutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unableto load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)--
Regards,
Stephane Kergozien
BEA Support

Error in Starting the Applicaion in DEBUG mode.

Hi all,
I am trying to DEBUG the Jave application in NETWEAVER DEVELOPMENT STUDIO. I am getting the Error REMOTE VM NOT CONNECTED.
If I am getting any tips to solve the error in DEBUG
I can proceed further.
Thanks in Advance.
Regards,
Ram

Hi,
did you follow the Debugging J2EE Applications tutorial located at http://help.sap.com/saphelp_nw04/helpdata/en/66/547f09281d464b951c9a3a6b06a12d/frameset.htm ? It tells you how to run your server node in debug node and debug the application from the developer studio.
Message was edited by: Ivaylo Ivanov

Adobe Photoshop CS6 provides no engine for debugging

Hello,
I've been trying to diagnose a problem with my wife's copy of CS6 Web and Design premium. Basically it's unable to run any JSX script that requires the Debug engine. I receive the error message 'Adobe Photoshop CS6 provides no engine for debugging' - trying it on Illustrator also gives a similar error. Persisting by clicking the 'play' button brings up a popup error message that says 'Unable to Run Script' or something similar.
Note that if I hack our JSX script to bypass the debug engine it works fine - except certain PSDs will cause CS6 (and my older copy of CS4) to crash, so this is only a stopgap measure. Disabling OpenGL on CS4 seems to prevent crashing but it's not an option on the wife's copy since she's a full-time artist and I'm not.
This is what I've had to change -
$.level = 2; // debug level: 0-2 (0:disable, 1:break on error, 2:break at beginning)
debugger; // launch debugger on next line
Changing the $.level = 0 lets me continue without issue.
This problem does NOT exist on my laptop using the same installer downloaded from Adobe.com. (I use trial version for testing, she uses her serial no.)
Is it possible this problem persists because I uninstalled an old copy of Photoshop CS5 (standalone installation) AFTER installing CS6 Web & Design (multiple programs)?
I've tried uninstalling and reinstalling CS6, but the problem persists.
Please help, our jobs rely on this. >.<
Worst case scenario I'll copy the entire install folder over from my laptop to try and fix the problem but I'd rather not have to since we're currently working in different countries and I can only use Remote Assistance to help.

The problem is the SCRIPTS work - the debugging engine is what's missing for some reason. Even if there's a way to just cleanly uninstall everything so I can start from scratch without formatting the hard disk would be a good solution. (since apparently I think I missed some files somewhere on the last uninstall)

In Debugging how can we view the normal data instead of Hexadecimal data

While i am debugging if i am checked internal table structure fields. Hexa decmial data is coming up. how can we check normal data.

If u r using Standard Debugger (Old Debugger) U will have a icon with + or - (search button type) beside ur fields. Click that. If that is in + mode u will see ur actual data, if it is in - u will see Hexa data.
awrd points if helpful
Bhupal

Can't Run program in Debug Mode

To: [email protected]
cc:
Subject: Can't Run program in Debug Mode
Has anyone else experienced this problem? We have written a non-express
program that uses the Express generated services project as a supplier
plan. However, when we try running this program in debug mode about 50%
(or more) of the time we abend while Forte is trying to partition the
application. Since we have many database classes in our Business Model we
are wondering if Forte is timing out during the partition phase or if the
server partition is running out of memory . The following error messages
are produced by Forte. Any suggestions???
=======================
Error messages on client:
=======================
SYSTEM ERROR: Unable to start the partition testacadprogoffer_CL0_Part1 on
any
of the nodes to which it has been assigned. See the remainder of the
error
stack for more information.
Class: qqsp_ResourceException
Error #: [1602, 593]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
Last TOOL statement: method overview.StartApplication
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on node
admin2.
Class: qqsp_ErrorDescriptor
Error #: [1602, 592]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Lost contact with remote server while trying to load
partition
testacadprogoffer_CL0_Part1. Check server log file for more information
about
the specific problem.
Class: qqsp_ResourceException
Error #: [1301, 102]
Detected at: qqem_IPartitionAgent::Startup at 5
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: The connection to the partner was terminated by the
Communication
Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Tue Dec 02 12:56:00
Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
(object name Unnamed) from partition "Forte_Executor", (partitionId =
F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment CentralEnv
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Received close: Connection aborted (10053).
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
=======================
Log messages on server:
=======================
Attached to manager for node admin2.
aud Tue Dec 2 09:34:36 : Loading partition testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
aud Tue Dec 2 09:41:59 : Unloaded partition testacadprogoffer_cl0_Part2.
aud Tue Dec 2 09:49:44 : Loading partition testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
aud Tue Dec 2 10:00:12 : Unloaded partition testacadprogoffer_cl0_Part2.
aud Tue Dec 2 10:18:34 : Loading partition testacadprogoffer_cl0_Part3
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
aud Tue Dec 2 10:27:00 : Unloaded partition testacadprogoffer_cl0_Part3.
aud Tue Dec 2 10:47:03 : Loading partition
EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of agent
owner's partition.
aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
aud Tue Dec 2 11:09:26 : Unloaded partition
EvaluateApplRequirementsBO_CL0_Part1.
aud Tue Dec 2 12:36:14 : Loading partition testacadprogoffer_CL0_Part1
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
aud Tue Dec 2 12:45:17 : Unloaded partition testacadprogoffer_CL0_Part1.
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:49:01
Exception occurred (locally) on partition "Forte_Executor",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in application
"Forte Runtime", pid 14020 on node admin2 in environ
ment CentralEnv.
FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:48:57
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
ERROR: TMgr.RunThread: task cm.Recv failed terminating.
Probably caused by a FATAL exception.
David Wilbur email: [email protected]
University of Windsor phone: 519-253-3000 ext. 2779
Windsor, Ontario Canada
-----------------------------------------------

Hi,
We have had the same problem in a non-express application
with a heavy server partition. In our case, the error was not
systematic, depending on the server workload at the time we
tried to partition and run.
The work-around we're using is to put the -fm flags (increasing the x
parameter to say 30000) in the 'server arguments' of your server
partition
properties in the partition workshop. Note that if your server is a Unix
platform,
you need to put double-quotes before and after the parenthesis in the -fm
syntax.
Hope this helps,
Vincent Figari
BTW, what Forte version are you using ?
On Tue, 2 Dec 1997 13:44:24 -0500 "David Wilbur"<[email protected]>
writes:
>
>
>
>
>
To: [email protected]
cc:
Subject: Can't Run program in Debug Mode
Has anyone else experienced this problem? We have written a
non-express
program that uses the Express generated services project as a supplier
plan. However, when we try running this program in debug mode about
50%
(or more) of the time we abend while Forte is trying to partition the
application. Since we have many database classes in our Business
Model we
are wondering if Forte is timing out during the partition phase or if
the
server partition is running out of memory . The following error
messages
are produced by Forte. Any suggestions???
=======================
Error messages on client:
=======================
SYSTEM ERROR: Unable to start the partition
testacadprogoffer_CL0_Part1 on
any
of the nodes to which it has been assigned. See the remainder of
the
error
stack for more information.
Class: qqsp_ResourceException
Error #: [1602, 593]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
Last TOOL statement: method overview.StartApplication
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on
node
admin2.
Class: qqsp_ErrorDescriptor
Error #: [1602, 592]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Lost contact with remote server while trying to load
partition
testacadprogoffer_CL0_Part1. Check server log file for more
information
about
the specific problem.
Class: qqsp_ResourceException
Error #: [1301, 102]
Detected at: qqem_IPartitionAgent::Startup at 5
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: The connection to the partner was terminated by the
Communication
Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Tue Dec 02 12:56:00
Distributed method called:
qqrt_ForteExecAgentProxy.LoadPartition!6
(object name Unnamed) from partition "Forte_Executor",
(partitionId =
F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Network partner closed connection. This usually means
the
process at the other end of the wire failed. Please go look there
and
find
out why.
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Received close: Connection aborted (10053).
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
=======================
Log messages on server:
=======================
Attached to manager for node admin2.
aud Tue Dec 2 09:34:36 : Loading partition
testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
aud Tue Dec 2 09:41:59 : Unloaded partition
testacadprogoffer_cl0_Part2.
aud Tue Dec 2 09:49:44 : Loading partition
testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
aud Tue Dec 2 10:00:12 : Unloaded partition
testacadprogoffer_cl0_Part2.
aud Tue Dec 2 10:18:34 : Loading partition
testacadprogoffer_cl0_Part3
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
aud Tue Dec 2 10:27:00 : Unloaded partition
testacadprogoffer_cl0_Part3.
aud Tue Dec 2 10:47:03 : Loading partition
EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of
agent
owner's partition.
aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
aud Tue Dec 2 11:09:26 : Unloaded partition
EvaluateApplRequirementsBO_CL0_Part1.
aud Tue Dec 2 12:36:14 : Loading partition
testacadprogoffer_CL0_Part1
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
aud Tue Dec 2 12:45:17 : Unloaded partition
testacadprogoffer_CL0_Part1.
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
FATAL ERROR: ************* Out of Memory, requested (1K) available
(0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:49:01
Exception occurred (locally) on partition "Forte_Executor",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in
application
"Forte Runtime", pid 14020 on node admin2 in environ
ment CentralEnv.
FATAL ERROR: ************* Out of Memory, requested (1K) available
(0K)
Class: qqsp_ResourceException with ReasonCode:
SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:48:57
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
ERROR: TMgr.RunThread: task cm.Recv failed terminating.
Probably caused by a FATAL exception.
David Wilbur email: [email protected]
University of Windsor phone: 519-253-3000 ext. 2779
Windsor, Ontario Canada

Can not view contents of variable in debug mode (version 1.1.1.5.0)

Hi
I am running on WebLogic 11R1 and using OEPE 1.1.1.5.0.
When Fast swap is enabled and I run WebLogic in debug mode using OEPE I can not view the contents of variables with the Eclipse debugger. I get the message "Expressions must contain either an expression or a block containing a well formed statement"
However, if I disable Fast swap, i can view the variable within the Eclipse debugger
Has anyone else had this problem?
Regards
Steve H

Small correction... the soon-to-be-released version of WebLogic Server that Danny was referring to is 11gR1 PatchSet 2 or 10.3.3.

Debugging avahi

Similar Messages

Maybe you are looking for