Debug.log : How do I analyze an orphaned transaction?

1

An orphan transaction is a transaction that consumes a coin whose creating transaction is not known to your client. This has nothing to do with orphan blocks (which are blocks whose parent block is not known, or according to another definition, blocks that are no longer part of the best chain).

Orphan transactions are not part of a block (they cannot be verified until their parents are known, and only valid transactions are allowed in blocks), and are kept in memory in the client. When their parents become known, and they are found valid, they are moved to the memory pool (which is - as the name suggests - also kept in memory only). From there, they are considered to be included in new blocks (if you're mining).

This piece of debug.log tells you that there are 3 transactions received (separate transactions, not part of a block) that reference some inputs that aren't known. Because of this, they are stored in the orphan pool, which grows as a result of that. "mapsz"...

0 0
2

lets repeat this info every few pages :

Quote from Evan : https://darkcointalk.org/threads/rc4-launch.2033/

Hello Everyone,

We're happy to announce that RC4 is now available for download.

This update includes a complete rewrite of the Darksend protocol, which vastly improves transaction privacy and removes the 10 DRK limit for Darksend transactions.
Please read this statement carefully as there are some new features in the RC4 wallet GUI that you need to know about before using it. Links to binaries and source are included at the end.

Information about changes to the functionality of Darksend in RC4 can be found here:

https://darkcointalk.org/threads/development-updates-july-15th.1788/
https://darkcointalk.org/threads/development-update-july-30th.1924/

Main wallet screen:

The main wallet screen now shows the amount of anonymized Darkcoin the user has available to send. There is no longer an artificial limit on the...

0 0
3

Error during Roll Back Packages – CRIMA1025E: Cannot create symbolic link

My dear debuggers,

Here is a small posting about a problem I have seen last week.

A user tried to roll back his BPM installation. The upgrade itself to BPM 8.5.7. CF2017.03 succeeded but later, for any reason the customer wanted to roll back to the pre-upgrade version.

From IBM Installation Manager he called the roll back option but received following exception

I requested the rollback.log file from customers environment (IBM Installation Manager) and could see the error:

...

Error during "post-install configure" phase:

0 0
4

The stock/requirements list (transaction MD04) displays all the MRP relevant documents and is builded with information from many different tables, belonging to different application areas (PP, MM, SD, QM, etc). Sometimes we don’t know exactly where a planning element is comming from or why is it displayed with a certain quantity or on a certain date. In these cases, the only way to resolve the issue is to analyze MD04 in debug.

The starting point to analyze MD04 in debug is function module AUFBAUEN_MDPSX_ANZEIGEN. Here, all the customizing, master data and planning elements are read from the database, therefore, we should set a break point o the beginning of this function module.

Initially, system reads the material master settings and MRP customizing (both methods of BAdI MD_MRP_PARAMETERS are called here), on the following piece of code:

After that, for each kind of planning element there is an specific SELECT form, like SELECT_PLAF, SELECT VBBE,...

0 0
5

How do I enable BCAAA debug logging?
How do I export BCAAA debug logs to a file?
My support engineers needs a debug log.
How do I turn on a BCAAA debug log?

How do I enable BCCA (Blue Coat Cloud Auth) debug logging?

Please only enable BCAAA debug logging when asked to do so by Blue Coat Technical Support. The debug log should only run long enough to collect data for the problem that is occurring. Then the debug log should be turned off. On your Windows server, please do the following steps:

Go to the %ProgramFiles%\Blue Coat Systems\BCAAA\ directory

The installation folder depends on what you chose during the installation process. Please refer to 000011179 for further details.

Open/Edit the BCAAA.ini file in that directory. Go to the bottom of the BCAAA.ini file and add the following lines:

[Debug]
DebugLevel=0xFFFFFFFF

Save your changes. Click on Start > Run > and type in "services.msc". The Windows Services will open up. ...
0 0
6

Introduction

Context

As SQL Server database administrators, we should all know that, most of the time, a database user is linked to a SQL Server login. We do this to tell SQL Server that a SQL login LoginA has access to database Db1 using the context and permissions of UserA database user.

There are exceptions like the two following ones:

LoginA has very high permissions at server level like being member of sysadmin role Db1 is self-contained, which means that it uses its own authentication and does not deal with SQL Logins. (SQL Server 2012+)

We might think that this linkage is done by matching names, but it’s not the case. Normalization comes in and this mapping is actually stored using a unique identifier called “SID”:

We can check SIDs for all our server principals using the following query :

If we look at documentation page of the sys.server_principals view, we can see that :

The principal_id is like an...
0 0
7

i am new to Django and web-faction.

I am trying to deploy a django project to production on webfaction

i performed all settings as per django tuts .

syncdb did not gave me any error on the terminal.

navigate to the site it gives this error

200 Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log.

i found that there were logs in Apache folder . also there were logs in folders called user and fronted in my username directory at top level. which logs do i see.

what is the meaning of access logs in user directory ? error logs in user directory ? access logs in front end directory ? error logs in front end directory ? logs folder in Apache...

0 0
8

Sometimes daemon.debug.log and other LOG system errors can be related to problems in the Windows registry. Several programs can share the same daemon.debug.log file, but when these programs are uninstalled or changed, sometimes "orphaned" (invalid) LOG registry entries are left behind.

Basically, what this means is that while the actual file path may have changed, its incorrect former location is still recorded in the Windows registry. When Windows tries looking up these incorrect file references (file locations on your PC), daemon.debug.log errors can occur. In addition, malware infection may have corrupted the registry entries associated with Third-Party Application. Thus, these invalid LOG registry entries need to be repaired to fix the root of the problem.

Manually editing the Windows registry to remove invalid daemon.debug.log keys is not recommended unless you are PC service professional. Incorrectly editing your registry can stop your PC from functioning and...

0 0
9

Several weeks ago one of our customers encountered an issue in which an index maintenance job that had always completed successfully, began failing with each nightly run. While troubleshooting the issue, the customer ran the DBCC OPENTRAN command against the affected database and discovered that another session, which had been running for several days, might be blocking the index maintenance job and causing it to fail. After repeated attempts at killing the long running session failed, the customer contacted our team and asked for our assistance in resolving the issue.

The first thing we asked the customer to do was to run the DBCC OPENTRAN command again against the affected database to confirm that the long running session was still active. As expected, the long running session (spid 178) was still active and had a transaction start time of several days in the past that coincided with the time the index maintenance job began failing.

We then asked the customer to run...

0 0
10
Are there any free tools, just for the viewing purpose? I saw a lot of tools, but all too expensive. Quest Log Reader is priced at 4-digits. I found one but only works for SQL server 2000.

Well, you can use undocumented

DBCC LOG(, )

0: Return only the minimum of information for each operation -- the operation, its context and the transaction ID. (Default)
1: As 0, but also retrieve any flags and the log record length.
2: As 1, but also retrieve the object name, index name, page ID and slot ID.
3: Full informational dump of each operation.
4: As 3 but includes a hex dump of the current transaction log row.

You can also use fn_dblog Even though usage is cumbersome it can still give you some good...

0 0
11

The IIS Diagnostics Debug Diagnostics Tool includes a feature that can provide a basic analysis of a captured memory dump file. To perform an analysis of a memory dump file follow these steps.

To analyze the dump file

Launch the Debug Diagnostics tool from Start, Programs, IIS Diagnostics, Debug Diagnostics Tools, Debug Diagnostics Tool 1.0.

Click the Advanced Analysis tab.

Under Available Analysis Scripts click to select Crash/Hang Analyzers to analyze a crash/hang dump or click to select Memory Pressure Analysis to analyze a memory dump of a process suspected of leaking memory.

Click the Add Data Files button to browse to the generated dump file and click the Open button to add the dump file to the possible list of data files to be analyzed.

Click to select the dump file that was added.

Click the Start Analysis button.

Once the analysis is complete a report is generated in .mht file format and displayed in Internet...

0 0
12
...
0 0
13

Hello Meinolf

The PDC Emulator is virtual (in this case it is an SBS 2011), and clock skew has been a problem previously both in this installation, as well as in other virtual environments. Currently, time sync works again (against an NTP pool), but we have experienced already two times on this server that time sync stops working, and the whole domain comes out of sync.

In order to find the root cause we have now enabled debug logging, and were hoping to find useful information. What should I look for in the debug log file?

/Maurice

Hello,

have you reset the time back to default and started again with w32tm configuration commands?

Do you work with GPOs for time sync in the domain?

What about the firewall port?

Does the server use more then one NIC/IP address?

Best regards

Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/

Disclaimer:...

0 0
14

1) Set up profiles for the User / Responsibility to be used to reproduce the issue

Responsibility: System Administrator
Navigation: Profile > System

Query up the Application, Responsibility and User you will use to reproduce the issue you want to debug.
For example:
Application = Receivables
Responsibility = Receivables Manager
User = MYUSER1
Profile = FND%Debug%

then set the profiles as shown below:

Following are examples on how you would set the above profiles depending on what you want to debug :

sample setting to debug everything :

FND: Debug Log Enabled YES
FND: Debug Log Filename NULL
FND: Debug Log Level STATEMENT
FND: Debug Log Module %

sample setting to debug ONLY Receivables :

FND: Debug Log Enabled YES
FND: Debug Log Filename NULL
FND: Debug Log Level STATEMENT
FND: Debug Log Module ar%

2) Since the debugging routine will start writing messages to...

0 0
15

Ned here again. Today begins a 21-part series on using the DFSR debug logs to further your understanding of Distributed File System Replication. While there are specific troubleshooting scenarios that will be covered, the most important part of understanding any products logging is making sure you are comfortable with it before you have errors. That way you have some point of reference if things go wrong.

As you can probably guess, these posts were a long time in development. They are based on an internal DFSR whitepaper I have worked on for six months, and which went through review by a number of excellent folks here in Support, Field Engineering, and the Product Group itself. Except for the removal of all private source code references, this series is otherwise unchanged.

I’ll start with a couple posts on the logs themselves, how they are formatted, how they can be controlled, etc. Then I’ll dig into scenarios in detail, for both Windows Server 2003 R2 and Windows...

0 0