Hi All ,
I try to install some packages in my global zone...
On the execution of the installion of the script it quits by saying the error
"Non global zone check failed"
Kindly help me in this regard
Thanks in advance,
jeganr (7 Replies)
Hi, Here is the questions: inetd on this Solaris 10 zone fails to start at boot time. Inetd has 4 dependents not started. These 4 dependents have their own dependents not started. How it happened? How can I use one or a few command to start inetd and all its dependents and dependents' dependents?... (11 Replies)
inet not running on the zone , below is the error we see on svc log
Importing 100235_1-rpc_ticotsord.xml ...Done
inetconv: Error reading from repository
inetconv: Notice: Service manifest for 100235/1 already generated as /var/svc/manifest/network/rpc/100235_1-rpc_ticotsord.xml, skipped... (0 Replies)
I have configured three zones on Solaris-11. These are non-global zones contain Solaris-11 only. One of the zone is not booting up, complaining about IP address in use, while it is not.
root@tdpdmsp02 # zoneadm list -icv
ID NAME STATUS PATH BRAND IP... (3 Replies)
I want a solaris zone,wich can get ip from dhcp external server
i configure my zone
net:
address not specified
allowed-address not specified
configure-allowed-address: true
physical: vnic1
defrouter not specified
vnic is linked to net0
dladm
net0 ... (6 Replies)
Dear all,
recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes.
I did the following:
host1:
$ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed
$ zpool export zone1
host2:
$ zpool... (2 Replies)
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Hi, hoping someone can help, its been a while since I used Solaris.
After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin)
However, the NGZ cannot access any other netwqork devices, it can't even see the default router
... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
LEARN ABOUT DEBIAN
doveadm-log
DOVEADM-LOG(1) Dovecot DOVEADM-LOG(1)NAME
doveadm-log - Locate, test or reopen Dovecot's log files
SYNOPSIS
doveadm [-Dv] log errors
doveadm [-Dv] log find [directory]
doveadm [-Dv] log reopen
doveadm [-Dv] log test
DESCRIPTION
The doveadm log commands are used to locate and reopen the log files of dovecot(1). It's also possible to test the configured targets of
the *log_path settings.
OPTIONS
Global doveadm(1) options:
-D Enables verbosity and debug messages.
-v Enables verbosity, including progress counter.
COMMANDS
log errors
doveadm log errors
The log errors command is used to show the last - up to 1,000 - errors and warnings. If no output is generated, no errors have occurred
since the last start.
log find
doveadm log find [directory]
The log find command is used to show the location of the log files, to which dovecot(1) sends its log messages. If dovecot(1) logs its
messages through syslogd(8) and doveadm(1) could not find any log files, you can specify the directory where your syslogd writes its log
files.
log reopen
doveadm log reopen
This command causes doveadm to reopen all log files, configured in the log_path, info_log_path and debug_log_path settings. These settings
are configured in /etc/dovecot/conf.d/10-logging.conf.
This is for example useful after manually rotating the log files.
log test
doveadm log test
This command causes doveadm to write the message "This is Dovecot's priority log (timestamp)" to the configured log files. The used prior-
ities are: debug, info, warning, error and fatal.
EXAMPLE
This example shows how to locate the log files used by dovecot(1).
doveadm log find
Looking for log files from /var/log
Debug: /var/log/dovecot.debug
Info: /var/log/mail.log
Warning: /var/log/mail.log
Error: /var/log/mail.log
Fatal: /var/log/mail.log
REPORTING BUGS
Report bugs, including doveconf -n output, to the Dovecot Mailing List <dovecot@dovecot.org>. Information about reporting bugs is avail-
able at: http://dovecot.org/bugreport.html
SEE ALSO doveadm(1)Dovecot v2.1 2012-02-22 DOVEADM-LOG(1)