10-01-2014
I believe appender for EventCounter need to define again it's look like it's didn't got initialing properly.once you made changes do rolling restart of your cluster.
9 More Discussions You Might Find Interesting
1. Solaris
Hi,
I upgraded solaris 10 x86 from update 3 to update 7 with zones installed n UFS file system . The global zone was updated but the non global zone still shows update 3 what could be the reason for this and how can i update the local zones to update 7 (0 Replies)
Discussion started by: fugitive
0 Replies
2. Solaris
I 'm running solaris10 u6 with 141414-02. My system is T5220 running 2 Ldoms and 7 zones on primary domain. I 'm tryin to create booth environment on my alternate root disk after breaking the SVM mirroring but it does not go well and stuck at some point , and i have to reboot the system to get rid... (1 Reply)
Discussion started by: fugitive
1 Replies
3. Solaris
I have created a solaris10 update9 zfs root flash archive for sun4v environment which i 'm tryin to use for upgrading solaris10 update8 zfs root based server using live upgrade.
following is my current system status
lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now... (0 Replies)
Discussion started by: fugitive
0 Replies
4. Solaris
Hi, I was trying to upgrade firmware for this Sun x4150 from ELOM to ILOM. I did it under GUI ELOM Manager > Maintenance > Firmware Upgrade. It then showed 'Someone is upgrading firmware' and took forever. I believe its hung due to unknown reason (wrong file used?). I poweroff and poweron the... (4 Replies)
Discussion started by: aixlover
4 Replies
5. Solaris
I tried a live upgrade for one my solaris 10u8 server which didnt go sucessfull and after that i now have following mounts in memory.
df: cannot statvfs /.alt.sol10u8_2/var: No such file or directory
df: cannot statvfs /.alt.sol10u8_2/var/run: No such file or directory
df: cannot statvfs... (0 Replies)
Discussion started by: fugitive
0 Replies
6. AIX
We recently upgraded 2 of our AIX 6.1 servers from TL4 to TL5.
Both servers are on the same p7 780 frame, installed at the same time from the same image. Both servers are mounting the same nfs share after reboot what worked perfectly fine until the upgrade.
Since the patching, one of the two... (5 Replies)
Discussion started by: zxmaus
5 Replies
7. Solaris
Hi Guys, having an issue with running Live Upgrade on a t5240 runiing Solaris 10 5/08.
The system has the required patches 121430, and Live upgrade was updated from the install media sol-10-u10-ga2-sparc-dvd.iso
The following boot environments were created
solenv1 and solenv2 with the... (8 Replies)
Discussion started by: Revo
8 Replies
8. Solaris
I have Solaris-10 sparc box with ZFS file-system, which is running two non global zones. I am in process of applying Solaris Recommended patch cluster via Live Upgrade.
Though I have enough space in root file-system of both zones, everytime I run installcluster, it fails with complaining less... (7 Replies)
Discussion started by: solaris_1977
7 Replies
9. UNIX for Dummies Questions & Answers
Hi team ,
I am trying to submit a simple ssh program using oozie but failing with below error .
AUTH_FAILED: Not able to perform operation | ErrorStream: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
i have validated that root@hostname has ssh access and i ... (3 Replies)
Discussion started by: Tomlight
3 Replies
LEARN ABOUT DEBIAN
ditrack
DITRACK(1) General Commands Manual DITRACK(1)
NAME
dt - DITrack command line client tool
SYNOPSIS
dt command [options] [args]
dt-createdb repository-url issue-db-dir local-wc
dt-upgrade-0.7-db issue-db-dir
OVERVIEW
DITrack is a free, open source, lightweight, distributed issue (bug, defect, ticket) tracking system using a Subversion repository instead
of a backend database. It is written in Python and runs in UNIX environment (*BSD, Linux, MacOS X).
The project is inspired by the idea of Subissue issue tracking system.
However, while Subissue aims in merely replacing the traditional database storage with Subversion repository, DITrack is a major rethought
of the issue tracking system paradigm. The main difference is that instead of sticking to the centralized model (one database, one web
interface, one mail integration machinery), DITrack treats underlying Subversion storage as a versioned distributed file system which
enables benefits of truly distributed operation mode.
For more information about the DITrack project, visit http://www.ditrack.org.
Documentation for DITrack and its tools, including detailed usage explanations of the dt and dt-createdb programs, can be found at
/usr/share/doc/ditrack/html/index.html.
Run `dt help' to access the built-in tool documentation.
Automatic upgrade is possible for databases created by DITrack 0.7. If you are upgrading from previous version of DITrack, use the upgrage
utility from DITrack 0.7 first.
To upgrade a database run the dt-upgrade-0.7-db script, passing the database path as the argument, like:
dt-upgrade-0.7-db /home/user/ditrack-database
The upgrade procedure merely modifies the working copy (nothing gets committed to the repository). So, when done, you should commit the
changes manually.
April 2007 DITRACK(1)