Solaris 10 zones - Resource Controls not persisting through reboot - Solaris Zones

Local zone was rebooted, but somehow the resource controls are not well configured and the oracle database did not start up.
The cat /etc/project shows this : The local zone has 10 gb. The oracle database was started manually with the startdb.sh, which conn /assysdba and issue a startup, adn also startups the listener.
cat /etc/project
system:0::::project.max-shm-memory=(privileged,8589934000,deny)
user.root:1::::project.max-shm-memory=(privileged,8589934000,deny)
noproject:2::::
default:3::::project.max-shm-memory=(privileged,6442450944,deny)
group.staff:10::::
user.oracle:100::oracle::project.max-shm-memory=(privileged,8589934000,deny)
group.dba:101::::project.max-sem-ids=(privileged,100,deny);project.max-shm-ids=(
privileged,100,deny);project.max-shm-memory=(privileged,6442450944,deny) 

Hi.
You don't say what resource controls is not configured correctly.
Login as user oracle
id -p
Say what project will be used.
prctl -i process $$
Print configured resource control.
See what wrong.
Regards. 

Nikolay, thank you for your reply.
What I know is that the zone was rebooted saturday. sunady at 1:00 am the oracle database (I'am a Dba not sysadmin), perform coldbackup (veritas.) then Veritas call a unix script to starts the database.
I run the script to starts the database manually sunday. Veritas could not open the database because of the Out of Memory.
The box has 10 gb , the oracle user, the rot and system are configured to use 8 gb, the rest are configured to use less.
I'am oracle user.
id -p
uid=100(oracle) gid=100(dba) projid=100(user.oracle)
prctl -i process $$
process: 8928: -ksh
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
process.max-port-events
privileged 65.5K - deny -
system 2.15G max deny -
process.max-msg-messages
privileged 8.19K - deny -
system 4.29G max deny -
process.max-msg-qbytes
privileged 64.0KB - deny -
system 16.0EB max deny -
process.max-sem-ops
privileged 512 - deny -
system 2.15G max deny -
process.max-sem-nsems
privileged 512 - deny -
system 32.8K max deny -
process.max-address-space
privileged 16.0EB max deny -
system 16.0EB max deny -
process.max-file-descriptor
basic 256 - deny 8928
privileged 65.5K - deny -
system 2.15G max deny -
process.max-core-size
privileged 8.00EB max deny -
system 8.00EB max deny -
process.max-stack-size
basic 8.00MB - deny 8928
privileged 8.00EB - deny -
system 8.00EB max deny -
process.max-data-size
privileged 16.0EB max deny -
system 16.0EB max deny -
process.max-file-size
privileged 8.00EB max deny,signal=XFSZ -
system 8.00EB max deny -
process.max-cpu-time
privileged 18.4Es inf signal=XCPU -
system 18.4Es inf none -
task.max-cpu-time
system 18.4Es inf none -
task.max-lwps
system 2.15G max deny -
project.max-contracts
privileged 10.0K - deny -
project.max-device-locked-memory
privileged 987MB - deny -
project.max-locked-memory
system 16.0EB max deny -
project.max-port-ids
privileged 8.19K - deny -
project.max-shm-memory
privileged 8.00GB - deny -
project.max-shm-ids
privileged 128 - deny -
project.max-msg-ids
privileged 128 - deny -
project.max-sem-ids
privileged 128 - deny -
project.max-crypto-memory
privileged 3.85GB - deny -
project.max-tasks
system 2.15G max deny -
project.max-lwps
system 2.15G max deny -
project.cpu-cap
system 4.29G inf deny -
project.cpu-shares
privileged 1 - none -
zone.max-swap
privileged 20.0GB - deny -
zone.max-locked-memory
system 16.0EB max deny -
zone.max-shm-memory
system 16.0EB max deny -
zone.max-shm-ids
system 16.8M max deny -
zone.max-sem-ids
system 16.8M max deny -
zone.max-msg-ids
system 16.8M max deny -
zone.max-lwps
system 2.15G max deny -
zone.cpu-cap
system 4.29G inf deny -
zone.cpu-shares
privileged 1 - none -
Print configured reso
urce control
ksh: Print: not found 

Hi
Current resourse control look like OK.
project.max-shm-memory privileged 8.00GB - deny -
Check that system have available memory:
swap -s
ipcs -a
vmstat 1 2
Regards,
Nikolay

Related

Quotas

We are running Store backends with mmp frontends, communicating over LMTP.
imsimta version:
Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)
libimta.so 7.0-3.01 64bit (built 09:24:13, Dec 9 2008)
Using /opt/sun/comms/messaging64/config/imta.cnf
SunOS mmp-sby1.its.utas.edu.au 5.10 Generic_138889-06 i86pc i386 i86pc
I am trying to get a quota regime setup so that:
- quota notifications are sent at 80% usage.
- Mail is rejected (rather than queued) when it would send a user overquota.
I have the noexquota set on the tcp_lmtpcs channel on the MMP MTA front end.
If I set the following configuration on the message store:
local.store.overquotastatus = on
local.store.quotaoverdraft = on
store.defaultmailboxquota = 314572800
store.defaultmessagequota = -1
store.quotaenforcement = on
store.quotaexceededmsg = "Subject: Overquota Warnin$$The diskquota for your ac count [ID] has been exceeded$$Your allocated disk space is [QUOTA], and you have used [DISKUSAGE].$$Please remove messages."
store.quotagraceperiod = 0
store.quotanotification = yes
store.quotawarn = 80
The notification is NOT sent at 80%, and the user's quota is allowed to go overquota, at which time the notification IS sent. If I unset overquotastatus, quotaoverdraft and quotgraceperiod, the notification IS sent at 80%, but the mail is queued if it would take the user overquota (despite the noexquota on the channel).
What am I missing?
Dave.
Edited by: brett_ac on May 27, 2009 8:27 PM 
brett_ac wrote:
The notification is NOT sent at 80%, and the user's quota is allowed to go overquota, at which time the notification IS sent. If I unset overquotastatus, quotaoverdraft and quotgraceperiod, the notification IS sent at 80%, but the mail is queued if it would take the user overquota (despite the noexquota on the channel).This is expected behaviour:
http://wikis.sun.com/display/CommSuite/Managing+Message+Store+Quotas
"Note: When local.store.quotaoverdraft=on email notifications are not triggered until the user’s disk usage exceeds 100% of the quota regardless of the threshold set with store.quotawarn."
If you want to send overquota information to your users, you can use the imquotacheck utility:
http://wikis.sun.com/display/CommSuite/imquotacheck
For example:
=> Create the imquotacheck rulefile /opt/sun/comms/messaging/imq.rulefile
[General]
mailQuotaAttribute=mailquota
[rule1]
notificationTriggerPercentage=80
enabled=1
notificationInterval=3
messageFile=/opt/sun/comms/messaging/config/warning.txt=> Create the warning message /opt/sun/comms/messaging/config/warning.txt
Subject: [Warning] quota reached for %U%
Hello %U%,
Your quota: %C%
Your current mailbox usage: %M%
Your mailbox is now %Q% full. The folders consuming the most space are:
%R%.
Please clean up unwanted diskspace.
Thanks,
-Administrator=> Run the command "./imquotacheck -n -e" to send the notification message to users over 80%
You could then schedule the ./imquotacheck command to run once a day (or more then once if need be) e.g.
bash-3.00# ./configutil -o local.schedule.quota -v "0 8 * * * bin/imquotacheck -n -e"
OK SET
bash-3.00# ./refresh sched
Refreshing sched server 11338 ... doneHope that helps.
Regards,
Shane. 
Thanks Shane. This answers most of my questions, but...
At http://wikis.sun.com/display/CommSuite/Managing+Message+Store+Quotas, it states:
"To enable or disable quota enforcement:
configutil -o store.quotaenforcement -v [ on | off]
Note that over quota messages are saved in the MTA queues and a notification is sent to the sender stating that their messages was (sic) not delivered, but that a redelivery attempt will be made later."
This does not seem to be the case if overquotastatus is NOT set - i.e. if the message would send the user overquota, it is queued, but there is no notification to the sender. Only if overquostatus is set, and the user is overquota is a reject message sent back to the sender. At least that seems to be my experience.
Also, I notice you have set the notificationInterval=3 in your imq.rulefile, and the examples at http://wikis.sun.com/display/CommSuite/imquotacheck do the same. The doco indicates that this parameter is "hours". Is this really "hours" or "days", and how does this tie in with scheduling of the imquotacheck each day?
Thanks,
Dave. 
Shane,
I've setup the two files as you suggest on our Message Store.
/opt/sun/comms/messaging64/config/imq.rulefile: - (Note the .../config/... in the path - without it, imquotacheck complained)
[General]
mailQuotaAttribute=mailquota
[rule1]
notificationTriggerPercentage=80
enabled=1
notificationInterval=1
messageFile=/opt/sun/comms/messaging64/config/overquota_warning.txt
and /opt/sun/comms/messaging64/config/overquota_warning.txt:
Subject: WARNING - YOU ARE APPROACHING YOU EMAIL ACCOUNT STORAGE LIMIT
This email is to warn you that your email account %U%#postoffice.utas.edu.au is
approaching you allocated storage limit.
Your account is allocated %C% and you are currently using %M% (%Q% Full).
The folders consuming the most space are:
%R%
WHEN YOUR ACCOUNT REACHES ITS ALLOCATED STORAGE LIMIT, NO FURTHER EMAIL WILL BE
DELIVERED TO YOUR ACCOUNT.
To avoid missing messages please reduce your storage usage as soon as possible.
-
ServiceDesk.
I then run imquotacheck -n -e. I have one user who is at 83% usage (according to imquotacheck), but no notification is sent to that user, even with repeated attempts. I have also restarted the Message Store, but still no luck.
Dave. 
Shane,
More information. The user I have who is overquota:
imquotacheck -u wgruter
Name Quota(K) Usage(K) % Quota# Usage# % OverDate WarnDate
wgruter 300000 248436 82 - 58 - - -
You'll notice that this user is at 82% quota usage.
When I run imquotacheck -n -e -D, the output for this user is:
get_stuff_from_directory: (wgruter)
[Debug] set_quota, quota_val = -2
[Debug] set_quota to : 4294967294
[Debug] check_usr_qta: (name=wgruter) usg = 0, least_trggr = 80
[Debug] Processing: user/wgruter/Drafts
[Debug] Lastuser (wgruter) & this user (wgruter)
[Debug] Processing: user/wgruter/Sent
[Debug] Lastuser (wgruter) & this user (wgruter)
[Debug] Processing: user/wgruter/Trash
[Debug] Lastuser (wgruter) & this user (wgruter)
What's with the "set_quota to : 4294967294", and also the "check_usr_qta: (name=wgruter) usg = 0, least_trggr = 80". The usg is certainly not 0. Is this why I'm not getting any notifications sent?
I've also found that I have to disable the store.quotanotification in order for the -n option to imquotacheck to work. Done that, to no avail.
Dave.
Edited by: brett_ac on May 28, 2009 7:45 PM
Edited by: brett_ac on May 28, 2009 7:45 PM 
brett_ac wrote:
/opt/sun/comms/messaging64/config/imq.rulefile: - (Note the .../config/... in the path - without it, imquotacheck complained)This was a typo on my behalf.
I then run imquotacheck -n -e. I have one user who is at 83% usage (according to imquotacheck), but no notification is sent to that user, even with repeated attempts. I have also restarted the Message Store, but still no luck.Did you disable the store warning functionality:
http://wikis.sun.com/display/CommSuite/imquotacheck
"The delivery agent’s quota warning mechanism needs to be turned off in order for the imquotacheck -n command to work, because the imquotacheck and the delivery agent use the same element in the quota database to record last-warn time. To turn off the delivery agent’s quota warning, set store.quotanotification to off. "
You will need to restart the store after disabling quota notifications.
You can see the quota database field referred to in the above paragraph by running:
./imcheck -d quota.db | grep "^user/<uid>"
e.g.
bash-3.00# ./imcheck -d quota.db | grep "^user/shjorth"
user/shjorth                            9766      351              - 20090529084912              -         0-     0   6000     21              -              -              -The "20090529084912" field is the last quota warning field and is used to propagate the "WarnDate" e.g.
bash-3.00# ./imquotacheck -u shjorth
Name                 Quota(K) Usage(K)  %   Quota#  Usage#  %  OverDate WarnDate
-------------------- -------- -------- --- ------- ------- --- -------- --------
shjorth                  9766      351   3    6000      21   0        - 05/29/09
--------------------------------------------------------------------------------You can run the ./imquotacheck with the -D option to get debug information to determine why the user isn't being emailed e.g.
./imquotacheck -n -e -D > /tmp/debug.outRegards,
Shane 
I then run imquotacheck -n -e. I have one user who is at 83% usage (according to imquotacheck), but no notification is sent to that user, even with repeated attempts. I have also restarted the Message Store, but still no luck.Did you disable the store warning functionality:http://wikis.sun.com/display/CommSuite/imquotacheck
"The delivery agent’s quota warning mechanism needs to be turned off in order for the imquotacheck -n command to work, because the imquotacheck and the delivery agent use the same element in the quota database to record last-warn time. To turn off the delivery agent’s quota warning, set store.quotanotification to off. "
You will need to restart the store after disabling quota notifications.Yes, disabled quota notifications, and restarted message store before testing. Currently:
# configutil -p \* | grep -i quota
store.defaultmailboxquota = 307200000
store.quotaexceededmsg = "Subject: Overquota Warning$$The disk quota for your account [ID] has been exceeded.$$Your allocated disk space is [QUOTA], and you have used [DISKUSAGE].$$Please remove messages."So no quotanotification set.
>
>
You can see the quota database field referred to in the above paragraph by running:
./imcheck -d quota.db | grep "^user/<uid>"
e.g.
bash-3.00# ./imcheck -d quota.db | grep "^user/shjorth"
user/shjorth                            9766      351              - 20090529084912              -         0-     0   6000     21              -              -              -The "20090529084912" field is the last quota warning field and is used to propagate the "WarnDate" e.g.For my user:
imcheck -d quota.db | grep "^user/wgruter"
user/wgruter                          300000   248436              -              -              -         0-     0     -1     58 20090601070348              -              -bash-3.00# ./imquotacheck -u shjorth
Name                 Quota(K) Usage(K)  %   Quota#  Usage#  %  OverDate WarnDate
-------------------------
-------- ---
-----
------- ---
-----
--------
shjorth                  9766      351   3    6000      21   0        - 05/29/09
--------------------------------------------------------------------------------For my user:
u# imquotacheck -u wgruter
Name                 Quota(K) Usage(K)  %   Quota#  Usage#  %  OverDate WarnDate
-------------------- -------- -------- --- ------- ------- --- -------- --------
wgruter                300000   248436  82       -      58   -        -        -
--------------------------------------------------------------------------------which indicates to me that the WarnDate has not yet been set. There is something I'm not doing here, but I can't see it yet.
You can run the ./imquotacheck with the -D option to get debug information to determine why the user isn't being emailed e.g.
./imquotacheck -n -e -D > /tmp/debug.outYou'll notice I've used the -D flag from the output in my previous post.
Dave. 
Shane,
I think I might have found some more information on my problem. Can you comment, please?
Our users are provisioned with the mailQuota attribute set to -2, as per the Schema Guide:
If the mailQuota attribute is not specified, the system default quota is used. The system default
is specified in the server configuration parameter store.defaultmailboxquota.
.
.
The table further indicates that a value of -2 will utilise the system default.Our system default is:
store.defaultmailboxquota = 314572800
I've found that, if I set the mailQuota attribute for a user to 314572800, the notification IS sent. Also, if I unset the mailQuota attribute for the user, the notification is also sent.
Is this some bug in imquotacheck such that it doesn't know about being able to set mailQuota to -2?
Thanks,
Dave. 
brett_ac wrote:
Is this some bug in imquotacheck such that it doesn't know about being able to set mailQuota to -2?It is indeed a bug in imquotacheck. There is no code to handle the "-2" (use store default mailquota) or "-1" (unlimited mail quota) mailquota values for notifications.
I've logged a new bug for this issue:
bug #6846682 - "imquotacheck notification functionality does not correctly handle special quota values"
Please escalate with sun support for a fix (ask that the case be assigned to me).
Regards,
Shane. 
Thanks, Shane. I'm logging the job now.
Dave.

ulimit parameters - Setting File Descriptor parameter

Hi all,
how can i know the maximum allowed number that i can use to set the maximum number of file descriptor in the /etc/system file.
as i faced some problems while trying to set it to 999999999 so it seems that there some limitations on that number or it depends on the hardware or the solaris version.
thanks in advance. 
The following command will show you per process resource constraints including the current constraint as well as the maximum constraint:
# plimit $$
16386:  /bin/ksh
   resource              current         maximum
  time(seconds)         unlimited       unlimited
  file(blocks)          unlimited       unlimited
  data(kbytes)          unlimited       unlimited
  stack(kbytes)         8192            unlimited
  coredump(blocks)      unlimited       unlimited
  nofiles(descriptors)  256             65536
  vmemory(kbytes)       unlimited       unlimitedSolaris defaults to 256 file descriptors which happens to be a function of the maximum value for an unsigned char (uchar_t). While the 65536 happens to be the maximum value of an unsigned 32-bit integer (uint32_t). I'm guessing these constraints are capped at these values for backwards compatibility reasons, but I don't really know for sure. Anyway, traditionally you would issue the following "ulimit -n 65536" as a function of user limits. However with Solaris 10, we now can set process limits using "plimit -n 65536 <pid>". For example:
# plimit -n 65536 $$
# plimit $$
16386:  /bin/ksh
   resource              current         maximum
  time(seconds)         unlimited       unlimited
  file(blocks)          unlimited       unlimited
  data(kbytes)          unlimited       unlimited
  stack(kbytes)         8192            unlimited
  coredump(blocks)      unlimited       unlimited
  nofiles(descriptors)  65536           65536
  vmemory(kbytes)       unlimited       unlimitedI'm not familiar with /etc/system modifications. I think editing /etc/system has been deprecated - use prctl instead. Nevertheless, I do know that for Solaris 10, the maximum per process limit for file descriptors is 65536. The next example shows what the system-wide constraints are. For file descriptors, this value is: 2.15G (2,150,000).
# prctl $$
process: 16386: /bin/ksh
NAME    PRIVILEGE       VALUE    FLAG   ACTION                       RECIPIENT
<...snip...>
process.max-file-descriptor
        basic             256       -   deny                             16386
        privileged      65.5K       -   deny                                 -
        system          2.15G     max   deny                                 -
<...snip...>Good luck,
Tracy S. Brown 
thanks alot Tracy for your help and info.
my question now is
is it possible to increase this maximum value which is 65536 and if yes what is the maximum allowed number is it 2.15G ? 
The 65,536 limit is for non-privileged (aka not root) users and processes (that is, processes that don't run with a privileged user id). Solaris 10 support what it calls "unlimited" as you've seen via plimit. The following command examples show the mechanics for setting a process to unlimited. I am interpreting the "unlimited" setting to be up to the system wide constraints (2.15G). But this may not be the case, the 2.15 system-wide max descriptors might be for non-privileged processes.
You need to be root (or a project-based privileged account)
[uid=0(root)#nickle] [tbrown]: plimit $$
24921:  ksh
   resource              current         maximum
  time(seconds)         unlimited       unlimited
  file(blocks)          unlimited       unlimited
  data(kbytes)          unlimited       unlimited
  stack(kbytes)         8192            unlimited
  coredump(blocks)      unlimited       unlimited
  nofiles(descriptors)  256             65536
  vmemory(kbytes)       unlimited       unlimited
[uid=0(root)#nickle] [tbrown]: plimit -n unlimited $$
[uid=0(root)#nickle] [tbrown]: plimit $$
24921:  ksh
   resource              current         maximum
  time(seconds)         unlimited       unlimited
  file(blocks)          unlimited       unlimited
  data(kbytes)          unlimited       unlimited
  stack(kbytes)         8192            unlimited
  coredump(blocks)      unlimited       unlimited
  nofiles(descriptors)  unlimited       unlimited
  vmemory(kbytes)       unlimited       unlimitedGood luck,
Tracy S. Brown. 
hi all..!
as I get to restart the operating system, these paramaters are not lost?
thanks
best regards.
Max

Kernel questions

Hi,
I am trying to obtion kernel info using sysdef command but the output doesn't have semmap information.
What command can I use to get all the semaphore and Shared memory info apart from /etc/system?
Thanks. 
sysdef (1M) will print information if the module is loaded.
Hi nkadoor
SEMMAP parameter is defined in /etc/system file and I guess they should be loaded but when I ran sysdef I do not see any entry for semmap.
Any thought?
Thanks 
Hi nkadoor
SEMMAP parameter is defined in /etc/system file and I
guess they should be loaded but when I ran sysdef I do
not see any entry for semmap.
Any thought?I am confused here. Are you referring to a semaphore facility module (semsys)
or something else?
If it is semsys,
what does the following command return?
modinfo | grep semsys
>
Thanks
Hi,
I am using sysdef to query kernel parameter setup on my server. My thought was sysdef should display all the kernel parameter define in my /etc/system.
This what I have in my /etc/system:
forceload: sys/semsys
set semsys:seminfo_semmni=400
set semsys:seminfo_semmns=16384
set semsys:seminfo_semmsl=500
set semsys:seminfo_semopm=200
set semsys:seminfo_semvmx=32767
set semsys:seminfo_semmap=250
set semsys:seminfo_semmnu=400
set semsys:seminfo_semume=100
This what I got when ran sysdef:
$ /usr/sbin/sysdef | grep SEM
400 semaphore identifiers (SEMMNI)
16384 semaphores in system (SEMMNS)
400 undo structures in system (SEMMNU)
500 max semaphores per id (SEMMSL)
200 max operations per semop call (SEMOPM)
100 max undo entries per process (SEMUME)
32767 semaphore maximum value (SEMVMX)
16384 adjust on exit max value (SEMAEM)
This the output for modinfo:
$ /usr/sbin/modinfo | grep semsys
32 1026c227 2878 53 1 semsys (System V semaphore facility)
32 1026c227 2878 53 1 semsys (32-bit System V semaphore facil)
My question is what utiliy/command that I can use to query my kernel parameter on Sun server since sysdef doesn't display all the parameter? On HP-UX kmtune can do the task.
Thanks.
This tunable ( semmap) is obsoleted from Solaris 8 onwards.
If you have 2.7 and earlier version of Solaris, you can see this parameter.
HTH.. 
Hi nkadoor,
Thanks the feedback. 
Note: the System-V Interprocess Communication (SYSV IPC) configuration is
completely changed in Solaris 10. You will no longer set these parameters
via /etc/system. You will be able to set them dynamically as a sort of resource
management. This is a big improvement and long overdue.
For more information, see the Solaris 10 Tunable Parameters Reference
Manual http://docs.sun.com/db/doc/817-0404
-- richard
So...Amin1999 did you get what needs to be done to get the Kernal Parameters? If so pl. can you tell
what is the solution? I am also looking for similar information ...but didn't find much info ...However
it looks to me that we have to do the same by using resource control manager feature...I am not sure
how to do it though.
Thanks 
AS root :
# mdb -k
Loading modules: [ unix krtld genunix ip nfs ipc ptm logindmux ]
::systemforceload: drv/random
set c2audit:audit_load=0x1 [0t1]
set abort_enable=0x0 [0t0]
>
I have not used resource manager, but it seems that one just needs to append the appropriate resource control to the corresponding project in /etc/project file.
group.dba:101:::: process.max-shm-ids=500,process.max-sem-ids=256
I am having issues with shared memory writes failing and reads failing sometimes. (Sol 10b60).
Thanks
So...Amin1999 did you get what needs to be done to
get the Kernal Parameters? If so pl. can you tell
what is the solution? I am also looking for similar
information ...but didn't find much info ...However
it looks to me that we have to do the same by using
resource control manager feature...I am not sure
how to do it though.
Thanks 
When I have run the sysdef -i, it shows "IPC Semaphores module is not loaded".
If the semaphores do not load, Is there anyway that I can execute it to make it load?

Advice needed about configuring access logs.

We got caught recently with a request to review the ODSEE access at 12:00:00 on 5.7.2012. Our out-of-the box access log configuration gave us a month (so I thought) of access history. The log parameters are:-
bash-3.2$ /opt/sfw/bin/sudo /opt/odsee/dsee7/bin/dsconf get-log-prop -h localhost -p 389 access
Enter "cn=Directory Manager" password:
buffering-enabled : on
enabled : on
level : default
max-age : 1M
max-disk-space-size : 500M
max-file-count : 10
max-size : 100M
min-free-disk-space-size : 5M
path : /opt/stmdirs/stmldap1/logs/access
perm : 600
rotation-interval : 1d
rotation-min-file-size : unlimited
rotation-time : undefined
verbose-enabled : N/A
This I gather means a maximum log file size of 500 Mb which may be spread over 10 files.
We have negotiated with the providers of the host machine to get 10GB of their disk we can use for logs. I hope to split this 7GB for access and 3GB for errors. 1 month max age is acceptable.
What would be the "best" settings to achieve this?? Any advice welcomed.
*HH                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                
Hi,
the official product documentation says that:
max-disk-space-size: This property defines the maximum disk space the specified type of log is allowed to consume. When the limit is reached, the server deletes the oldest log file to reclaim disk space.
note the words "the specified type of logs".
This means thatis you set:
$ dsconf set-log-prop ACCESS max-disk-space-size:7G
you set the 7 gigabytes limit for the access log; as well as, if you set
$ dsconf set-log-prop ERROR max-disk-space-size:3G
you set the 3 gigabytes limit for the error log.
HTH,
Marco 
Ok. one setting fixes the total log size.
So what I should do for access logging is to have
total size = 7GB
held in 10 files
each file 650MB
what confuses me now is the rotations.
If the system is tracking the log by size and filling up each file one by one and switching to next when log file size reaches 650Mb what value is there for a rotation or even max age?

Tuxedo logging problem

Hello, we are using Tuxedo 10gR3 on HP-UX and we still have a logging problem. tuxconfig:auth    SRVID=2100 MIN=10 MAX=15 CLOPT="-A -e ../log/auth.out -o ../log/auth.out" RQADDR="auth1" REPLYQ=Y RESTART=Y so auth will log into auth.out. That works fine. But if auth.out exceeds the limit of 2^31 Byte auth will stop logging into auth.out and if we set back the size of auth.out to 0 Byte (cat /dev/null > auth.out)auth will continue logging not until we restart this process. Is there any posibility to continue logging without restarting auth? Greets from Germany,Mario I`m sorry for my english.

Categories

Resources