I am trying to import 25 packets from the incoming bay on my vob server.
An lspacket of each of the packet shows that the packets are fragments from 1 to 25.
Here's an example:
multitool lspacket sync_XXX_12977
Packet is: /clearcase/shipping/ms_ship/incoming/sync_XXX_12977
Packet type: Update
Packet fragment: 1 of 25
...
multitool lspacket sync_XXX_12977_6
Packet is: /clearcase/shipping/ms_ship/incoming/sync_XXX_12977_6
Packet type: Update
Packet fragment: 6 of 25
...and so on upto _25.
So to import all the fragments/packets at once, I did a syncreplica -import [all packets from sync_XXX_12977 to sync_XXX_12977_25].
With this I get an error like:
multitool: Error: Unable to write file "/var/tmp/syncs04042": No space left on device.
Can anyone please help me with this?
Also, I should mention that incoming packets for other vobs seem to have lesser number of fragments, and they are successfully imported by the scheduled sync_receive.
I'm not sure why this error is coming only for packets for this particular vob. Could it be because of larger number of fragments?
Here is some more info about the error:
multitool: Error: Vob server operation "Create Container" failed.
Additional information may be available in the vob_log on host "VOBserver.qwerty.com"
multitool: Error: Unable to create a container in vob "/vobs/products", because group "root" not in vob's group list.
multitool: Error: Unable to replay oplog entry 927736: Not owner.
927736:
op= checkin
replica_oid= 9c863907.23ca11e2.9baf.00:01:83:db:e4:2d (ABC_SW)
oplog_id= 659061
op_time= 2014-06-06T07:18:47Z create_time= 2014-07-31T09:18:01Z
version_oid= 8426e33c.ed4b11e3.931b.00:01:83:db:e4:2d (*no view*)
event comment= "created by clearfsimport"
data size= 116 data= 0x12e108
------------
ver_oid= 8426e33c.ed4b11e3.931b.00:01:83:db:e4:2d (*no view*)
ver_num= 1
ver_fstat= ino: 0; type: 1; mode: 00
usid: DONTCARE
gsid: DONTCARE
nlink: 0; size: 130017856
atime: Thu Jan 1 05:30:00 1970
mtime: Fri Jun 6 12:48:14 2014
ctime: Fri Jun 6 12:48:14 2014
ckout_ver_oid= 8426e33c.ed4b11e3.931b.00:01:83:db:e4:2d (*no view*)
I checked vob's properties using lsvob -long and desc: the vob owner and group are CC admin and ccgrp.
If those packets are particularly big, that might explain the "No space left on device" message.
The first check is to do a:
cd /var/tmp
df -h .
And check what space you have left to work.
Once that disk space issue is fixed, you should:
get the primary group of the vob (cleartool descr -l vob:/vobs/products)
check that id -a (for ccadmin) returns that group as primary group (meaning the first group displayed by that command should be the one of the vob)
Related
I'm using the Raspberry Pi 4 and trying to have an Internet access using the A9G GSM/GPRS+GPS Module.
At first I have install ppp with sudo apt-get install ppp screen elinks
I have create a file with name rnet in path /etc/ppp/peers/rnet:
# My APN internet.vodafone.gr
connect "/usr/sbin/chat -v -f /etc/chatscripts/gprs -T internet.vodafone.gr"
# Communication port:
/dev/ttyS0
# Baudrate
9600
# Assumes that your IP address is allocated dynamically by the ISP.
noipdefault
# Try to get the name server addresses from the ISP.
usepeerdns
# Use this connection as the default route to the internet.
defaultroute
# Makes PPPD "dial again" when the connection is lost.
persist
# Do not ask the remote to authenticate.
noauth
# No hardware flow control on the serial link with GSM Modem
nocrtscts
# No modem control lines with GSM Modem
local
In file gprs in path /etc/chatscripts/gprs I have add the line that need my "MY_4_DIGIT_PIN":
ABORT BUSY
ABORT VOICE
ABORT "NO CARRIER"
ABORT "NO DIALTONE"
ABORT "NO DIAL TONE"
ABORT "NO ANSWER"
ABORT "DELAYED"
ABORT "ERROR"
# cease if the modem is not attached to the network yet
ABORT "+CGATT: 0"
"" AT
TIMEOUT 12
OK ATH
OK ATE1
# +CPIN provides the SIM card PIN
OK AT+CPIN="MY_4_DIGIT_PIN"
# +CFUN may allow to configure the handset to limit operations to
# GPRS/EDGE/UMTS/etc to save power, but the arguments are not standard
# except for 1 which means "full functionality".
#OK AT+CFUN=1
OK AT+CGDCONT=1,"IP","\T","",0,0
OK ATD*99#
TIMEOUT 22
CONNECT ""
So when I'am trying to starts up the rnet file:
sudo pon rnet
I get this error message in syslog (cat /var/log/syslog | grep pppd):
Oct 14 18:14:22 raspberrypi pppd[3063]: pppd 2.4.7 started by pi, uid 0
Oct 14 18:14:35 raspberrypi pppd[3063]: Connect script failed
Oct 14 18:15:06 raspberrypi pppd[3063]: Connect script failed
Oct 14 18:15:37 raspberrypi pppd[3063]: Connect script failed
...
When I am trying to run the below AT commands, the module seems to be work fine and be able to connected to network:
AT
OK
AT+CPIN?
+CPIN:READY
OK
AT+CREG?
+CREG: 1,1
OK
AT+CGATT?
+CGATT:1
OK
AT+COPS?
+COPS: 0,2,"20205"
AT+CGACT?
+CGACT: 1, 1
AT+HTTPGET="http://www.example.com/"
OK
HTTP/1.1 200 OK
...
So I can't understand if I have have writing something wrong in file rnet or is something else that I am not doing it right. If you have any idea please help me.
The problem was that my A9G Module, was not getting enough power.
Therefore, check if your A9G Module is turned on, before starting the process
and make sure that you have disabled login shell to be accessible over serial,
and also you have enabled the serial interface.
I need to be connect to 2 STM32s over 2 ST-Links at the same time. I found this issue described here.
However, solution doesn't work for me.
ST-Link ID1: 55FF6B067087534923182367
ST-Link ID2: 49FF6C064983574951291787
OpenOCD cfg file:
source [find interface/stlink-v2.cfg]
hla_serial "55FF6B067087534923182367"
source [find target/stm32f4x.cfg]
# use hardware reset, connect under reset
reset_config srst_only srst_nogate
I get:
$ openocd.exe -f stm32f4_fmboard.cfg
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
none separate
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : clock speed 1800 kHz
Error: open failed
in procedure 'init'
in procedure 'ocd_bouncer'
I do not know if solved but:
pi#raspberrypi:~/prog/bootloader $ st-info --probe
Found 1 stlink programmers
serial: 363f65064b46323613500643
openocd: "\x36\x3f\x65\x06\x4b\x46\x32\x36\x13\x50\x06\x43"
flash: 0 (pagesize: 0)
sram: 0
chipid: 0x0000
descr: unknown device
this tool shows serial of st-links and there is option called openocd. When I put hla_serial "\x36\x3f\x65\x06\x4b\x46\x32\x36\x13\x50\x06\x43" in file then it works for me. Your way does not. It also does not work in command line given as argument. It works only as I described in cfg file
The format of the configuration file seems to have changed recently. The following applies for Open On-Chip Debugger 0.10.0+dev-00634-gdb070eb8 (2018-12-30-23:05).
Find out the serial number with lsusb, st-link, or with ls -l /dev/serial/by-id. The latter yields (with two STLink/V2.1 connected):
total 0
lrwxrwxrwx 1 root root 13 Nov 30 14:31 usb-STMicroelectronics_STM32_STLink_066CFF323535474B43125623-if02 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Dec 30 23:55 usb-STMicroelectronics_STM32_STLink_0672FF485457725187052924-if02 -> ../../ttyACM1
The specification on the .cfg-file is now plain hex. Do not use the C string syntax any longer. For selecting the latter device, simply write:
#hla_serial "066CFF323535474B43125623"
hla_serial "0672FF485457725187052924"
I am running CentOS 6.6 and I trying to figure out what might be causing gdm-password error to show up every 25 minutes in /var/log/messages log eventhough no user has attempted to login. Can someone please help me to understand what might be running every 25 minutes that could cause this error to occur.
Aug 25 00:10:22 TEST pam: gdm-password: pam_succeed_if(gdm-password:auth): error retrieving user name: Conversation error
Aug 25 00:10:22 TEST pam: gdm-password: gkr-pam: couldn't get the user name: Conversation error
Aug 25 00:10:22 TEST pam: gdm-password: pam_succeed_if(gdm-password:auth): error retrieving user name: Conversation error
Aug 25 00:10:22 TEST pam: gdm-password: pam_selinux_permit(gdm-password:auth): Cannot determine the user's name
I was able to determine that the below gconf setting was causing the gdm password error to show up every 25 minutes.
gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --set /desktop/gnome/session/max_idle_action --type string forced-logout
To Fix this I made sure the gconf setting was set as a regular user and not as root.
sudo -u username gconftool-2 --set /desktop/gnome/session/max_idle_action --type string forced-logout
We're attempting to use Zend_Ldap to authenticate users to our website using the subscriber's LDAP server. We have a couple clients already setup and working but when we added a new client the connection just hung and after 30 minutes(!) we received the following (less than helpful) error:
0x51 (Can't contact LDAP server): ldap://x.x.x.x
The only other debugging step I know is to use ldapsearch. If I do just ldapsearch -h x.x.x.x nothing happens for a very long time (I don't feel like waiting 30 minutes but I'm guessing I'll get the "Can't connect to LDAP server" error) and if I run it using -d5 I get the following output.
ldap_create
ldap_url_parse_ext(ldap://x.x.x.x)
ldap_extended_operation_s
ldap_extended_operation
ldap_send_initial_request
ldap_new_connection 1 1 0
ldap_int_open_connection
ldap_connect_to_host: TCP x.x.x.x:389
ldap_new_socket: 3
ldap_prepare_socket: 3
ldap_connect_to_host: Trying x.x.x.x:389
ldap_pvt_connect: fd: 3 tm: -1 async: 0
ldap_open_defconn: successful
ldap_send_server_request
ber_scanf fmt ({it) ber:
ber_scanf fmt ({) ber:
ber_flush2: 31 bytes to sd 3
ldap_result ld 0x7f9ad5666410 msgid 1
wait4msg ld 0x7f9ad5666410 msgid 1 (infinite timeout)
wait4msg continue ld 0x7f9ad5666410 msgid 1 all 1
** ld 0x7f9ad5666410 Connections:
* host: x.x.x.x port: 389 (default)
refcnt: 2 status: Connected
last used: Mon Jul 13 09:14:44 2015
** ld 0x7f9ad5666410 Outstanding Requests:
* msgid 1, origid 1, status InProgress
outstanding referrals 0, parent count 0
ld 0x7f9ad5666410 request count 1 (abandoned 0)
** ld 0x7f9ad5666410 Response Queue:
Empty
ld 0x7f9ad5666410 response count 0
ldap_chkResponseList ld 0x7f9ad5666410 msgid 1 all 1
ldap_chkResponseList returns ld 0x7f9ad5666410 NULL
ldap_int_select
<20+ minute delay>
read1msg: ld 0x7f9ad5666410 msgid 1 all 1
ber_get_next
ldap_err2string
ldap_start_tls: Can't contact LDAP server (-1)
ldap_free_request (origid 1, msgid 1)
ldap_free_connection 1 1
ldap_free_connection: actually freed
The client's LDAP server is Windows Server 2008 R2 and we're using Ubuntu 12.04.4 LTS with ldapsearch from OpenLDAP 2.4.28.
Any suggestions on what to troubleshoot next? My guess is it's somewhere in the clients network but I want to check my end as much as possible before I start asking them.
Update:
I added:
ldap_set_option(NULL, LDAP_OPT_DEBUG_LEVEL, 7);
to my php script and got the same output as what was returned from ldapsearch.
The long and the short of it is that the client's firewall was set to allow the connection but it was set with a different protocol so the deep packet inspection was knocking it down. Hopefully if this every happens to someone else this will be helpful.
I have freshly installed an application on solaris 5.10 . When checked through ps -ef | grep hyperic | grep agent, process are up and running . When checked the status through svcs hyperic-agent command, the output shows that the agent is in maintenance mode . Application is working fine and I dont have any issues with the application . Please help
There are several reasons that lead to that behavior:
Starter (start/exec property of service) returned status that is different from SMF_EXIT_OK (zero). Than you may check logs:
# svcs -x ssh
...
See: /var/svc/log/network-ssh:default.log
If you check logs, you may see following messages that means, starter script failed or incorrectly written:
[ Aug 11 18:40:30 Method "start" exited with status 96 ]
Another reason for such behavior is that service faults during while its working (i.e. one of processes coredumps or receives kill signal or all processes exits) as described here: https://blogs.oracle.com/lianep/entry/smf_5_fault_retry_models
The actual system that provides SMF facilities for monitoring that is System Contracts. You may determine contract ID of online service with svcs -v (field CTID):
# svcs -vp svc:/network/smtp:sendmail
STATE NSTATE STIME CTID FMRI
online - Apr_14 68 svc:/network/smtp:sendmail
Apr_14 1679 sendmail
Apr_14 1681 sendmail
Than watch events with ctwatch:
# ctwatch 68
CTID EVID CRIT ACK CTTYPE SUMMARY
68 28 crit no process contract empty
Than there are two options to handle that:
There is a real problem with service so it eventually faults. Than debug the application.
It is normal behavior of service, so you should edit and re-import your service manifest, to make SMF less paranoid. I.e. configure ignore_error and duration properties.