Linux / Unix Command: packet

Linux / Unix Command: packet
Command Library

NAME

packet, PF_PACKET - packet interface on device level.

 

SYNOPSIS

#include <sys/socket.h>


#include <features.h>   /* for the glibc version number */


#if __GLIBC__ >= 2 && __GLIBC_MINOR >= 1 


#include <netpacket/packet.h>


#include <net/ethernet.h>       /* the L2 protocols */


#else


#include <asm/types.h>


#include <linux/if_packet.h>


#include <linux/if_ether.h>     /* The L2 protocols */ 


#endif


packet_socket = socket(PF_PACKET, int socket_type, int protocol);
 

DESCRIPTION

Packet sockets are used to receive or send raw packets at the device driver
(OSI Layer 2)level. They allow the user to implement protocol modules in user space on top of the physical layer.

Thesocket_typeis either SOCK_RAW for raw packets including the link level header orSOCK_DGRAMfor cooked packets with the link level header removed. The link levelheader information is available in a common format in asockaddr_ll.protocol is the IEEE 802.3 protocol number in network order. See the<linux/if_ether.h> include file for a list of allowed protocols. When protocol is set tohtons(ETH_P_ALL)then all protocols are received.All incoming packets of that protocol type will be passed to the packetsocket before they are passed to the protocols implemented in the kernel.
 Only processes with effective uid 0 or theCAP_NET_RAWcapability may open packet sockets.

SOCK_RAWpackets are passed to and from the device driver without any changes inthe packet data. When receiving a packet, the address is still parsed andpassed in a standardsockaddr_lladdress structure. When transmitting a packet, the user supplied buffershould contain the physical layer header. That packet is thenqueued unmodified to the network driver of the interface defined by thedestination address. Some device drivers always add other headers.SOCK_RAWis similar to but not compatible with the obsolete SOCK_PACKETof Linux 2.0.

SOCK_DGRAM operates on a slightly higher level. The physical header is removed beforethe packet is passed to the user. Packets sent through aSOCK_DGRAMpacket socket get a suitable physical layer header based on the informationin the sockaddr_ll destination address before they are queued.

By default all packets of the specified protocol typeare passed to a packet socket. To only get packets from a specific interfaceusebind(2)specifying an address in astruct sockaddr_llto bind the packet socket to an interface. Only the sll_protocol and thesll_ifindexaddress fields are used for purposes of binding.

Theconnect(2)operation is not supported on packet sockets.

When theMSG_TRUNCflag is passed torecvmsg(2),recv(2),recvfrom(2)the real length of the packet on the wire is always returned, even when itis longer than the buffer.

 

ADDRESS TYPES

The sockaddr_ll is a device independent physical layer address.


struct sockaddr_ll {
    unsigned short  sll_family;    /* Always AF_PACKET */
    unsigned short  sll_protocol;  /* Physical layer protocol */
    int             sll_ifindex;   /* Interface number */
    unsigned short  sll_hatype;    /* Header type */
    unsigned char   sll_pkttype;   /* Packet type */
    unsigned char   sll_halen;     /* Length of address */ 
    unsigned char   sll_addr[8];   /* Physical layer address */
};

sll_protocol is the standard ethernet protocol type in network order as definedin thelinux/if_ether.hinclude file. It defaults to the socket's protocol.sll_ifindex is the interface index of the interface(seenetdevice(7));0 matches any interface (only legal for binding).sll_hatype is a ARP type as defined in the linux/if_arp.hinclude file.sll_pkttype contains the packet type. Valid types arePACKET_HOSTfor a packet addressed to the local host,PACKET_BROADCASTfor a physical layer broadcast packet,PACKET_MULTICASTfor a packet sent to a physical layer multicast address,PACKET_OTHERHOSTfor a packet to some other host that has been caught by a device driverin promiscuous mode, andPACKET_OUTGOINGfor a packet originated from the local host that is looped back to a packetsocket. These types make only sense for receiving.sll_addrandsll_halencontain the physical layer (e.g. IEEE 802.3) address and its length. The exact interpretation depends on the device.

When you send packets it is enough to specifysll_family,sll_addr,sll_halen,sll_ifindex.The other fields should be 0.sll_hatypeandsll_pkttypeare set on received packets for your information.For bind onlysll_protocolandsll_ifindexare used.

 

SOCKET OPTIONS

Packet sockets can be used to configure physical layer multicasting and promiscuous mode. It works by calling setsockopt(2)on a packet socket for SOL_PACKET and one of the options PACKET_ADD_MEMBERSHIP to add a binding or PACKET_DROP_MEMBERSHIPto drop it.They both expect a packet_mreqstructure as argument:


struct packet_mreq
{
    int             mr_ifindex;    /* interface index */
    unsigned short  mr_type;       /* action */
    unsigned short  mr_alen;       /* address length */
    unsigned char   mr_address[8]; /* physical layer address */ 
};

mr_ifindexcontains the interface index for the interface whose statusshould be changed.Themr_typeparameter specifies which action to perform.PACKET_MR_PROMISCenables receiving all packets on a shared medium - often known as``promiscuous mode'',PACKET_MR_MULTICAST binds the socket to the physical layer multicast group specified inmr_addressandmr_alen,andPACKET_MR_ALLMULTIsets the socket up to receive all multicast packets arriving at the interface.

In addition the traditional ioctls SIOCSIFFLAGS,SIOCADDMULTI, SIOCDELMULTIcan be used for the same purpose.

 

IOCTLS

SIOCGSTAMPcan be used to receive the time stamp of the last received packet. Argumentis a struct timeval.

In addition all standard ioctls defined innetdevice(7)andsocket(7)are valid on packet sockets.

 

ERROR HANDLING

Packet sockets do no error handling other than errors occurred while passingthe packet to the device driver. They don't have the concept of a pendingerror


====

http://linux.about.com/library/cmd/blcmdl7_packet.htm


2025-09-22 11:11:37.538: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[M], command ID:24557, data Length:124 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: received watchdog packet type:I 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: reading packet type I of length 369 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24557] type:[NODE INFO] state:[LEADER] 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: packet I with command ID 24557 is reply to the command M 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: Watchdog node "192.168.1.72:9999 Linux localhost.localdomain" has replied for command id 24557 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: command I with command id 24557 is finished with COMMAND_FINISHED_ALL_REPLIED 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = LEADER 2025-09-22 11:11:37.539: watchdog pid 902555: DEBUG: I am the cluster leader node command finished with status:[ALL NODES REPLIED] 2025-09-22 11:11:37.539: watchdog pid 902555: DETAIL: The command was sent to 1 nodes and 1 nodes replied to it 2025-09-22 11:11:37.548: watchdog pid 902555: DEBUG: received watchdog packet type:d 2025-09-22 11:11:37.549: watchdog pid 902555: DEBUG: reading packet type d of length 62 2025-09-22 11:11:37.549: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:37.549: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24954] type:[DATA REQUEST FOR LEADER] state:[LEADER] 2025-09-22 11:11:37.549: watchdog pid 902555: DEBUG: sending packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24954] type:[DATA] state:[LEADER] 2025-09-22 11:11:37.549: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[D], command ID:24954, data Length:110 2025-09-22 11:11:37.924: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:37.924: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:37.926: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:11:37.935: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:11:37.935: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:11:37.935: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:37.935: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:37.935: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:38.969: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:40.969: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:42.544: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:42.544: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:11:42.544: sr_check_worker pid 903049: DEBUG: watchdog status: 4 2025-09-22 11:11:42.544: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:42.544: watchdog pid 902555: DEBUG: received the get data request from local pgpool-II on IPC interface 2025-09-22 11:11:42.544: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:0 2025-09-22 11:11:42.544: sr_check_worker pid 903049: DEBUG: 1:0: Unexpected 2025-09-22 11:11:42.545: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:42.545: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:11:42.545: sr_check_worker pid 903049: DEBUG: quorum: 1 node_count: -1 2025-09-22 11:11:42.545: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: lock was not held by anyone 2025-09-22 11:11:42.545: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: succeeded in acquiring lock 2025-09-22 11:11:42.545: sr_check_worker pid 903049: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:42.547: sr_check_worker pid 903049: DEBUG: authenticate kind = 10 2025-09-22 11:11:42.555: sr_check_worker pid 903049: DEBUG: SCRAM authentication successful for user:rep 2025-09-22 11:11:42.555: sr_check_worker pid 903049: DEBUG: authenticate backend: key data received 2025-09-22 11:11:42.555: sr_check_worker pid 903049: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:42.555: sr_check_worker pid 903049: DEBUG: do_query: extended:0 query:"SELECT pg_catalog.pg_is_in_recovery()" 2025-09-22 11:11:42.556: sr_check_worker pid 903049: DEBUG: verify_backend_node_status: there's no primary node 2025-09-22 11:11:42.556: sr_check_worker pid 903049: DEBUG: node status[0]: 0 2025-09-22 11:11:42.556: sr_check_worker pid 903049: DEBUG: node status[1]: 2 2025-09-22 11:11:42.556: sr_check_worker pid 903049: DEBUG: pool_release_follow_primary_lock called 2025-09-22 11:11:42.935: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:42.936: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:42.938: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:11:42.946: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:11:42.947: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:11:42.947: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:42.947: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:42.947: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:42.969: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:44.969: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:46.970: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:47.550: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = LEADER 2025-09-22 11:11:47.550: watchdog pid 902555: DEBUG: sending packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24558] type:[IAM COORDINATOR] state:[LEADER] 2025-09-22 11:11:47.550: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[M], command ID:24558, data Length:124 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: received watchdog packet type:I 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: reading packet type I of length 369 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24558] type:[NODE INFO] state:[LEADER] 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: packet I with command ID 24558 is reply to the command M 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: Watchdog node "192.168.1.72:9999 Linux localhost.localdomain" has replied for command id 24558 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: command I with command id 24558 is finished with COMMAND_FINISHED_ALL_REPLIED 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = LEADER 2025-09-22 11:11:47.551: watchdog pid 902555: DEBUG: I am the cluster leader node command finished with status:[ALL NODES REPLIED] 2025-09-22 11:11:47.551: watchdog pid 902555: DETAIL: The command was sent to 1 nodes and 1 nodes replied to it 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: received watchdog packet type:d 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: reading packet type d of length 62 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24955] type:[DATA REQUEST FOR LEADER] state:[LEADER] 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: sending packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24955] type:[DATA] state:[LEADER] 2025-09-22 11:11:47.560: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[D], command ID:24955, data Length:110 2025-09-22 11:11:47.947: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:47.948: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:47.949: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:11:47.958: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:11:47.958: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:11:47.958: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:47.958: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:47.958: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:48.970: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:50.971: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:11:52.557: sr_check_worker pid 903049: DEBUG: watchdog status: 4 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: received the get data request from local pgpool-II on IPC interface 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:0 2025-09-22 11:11:52.557: sr_check_worker pid 903049: DEBUG: 1:0: Unexpected 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:11:52.557: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:11:52.557: sr_check_worker pid 903049: DEBUG: quorum: 1 node_count: -1 2025-09-22 11:11:52.558: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: lock was not held by anyone 2025-09-22 11:11:52.558: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: succeeded in acquiring lock 2025-09-22 11:11:52.558: sr_check_worker pid 903049: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:52.560: sr_check_worker pid 903049: DEBUG: authenticate kind = 10 2025-09-22 11:11:52.569: sr_check_worker pid 903049: DEBUG: SCRAM authentication successful for user:rep 2025-09-22 11:11:52.569: sr_check_worker pid 903049: DEBUG: authenticate backend: key data received 2025-09-22 11:11:52.569: sr_check_worker pid 903049: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:52.569: sr_check_worker pid 903049: DEBUG: do_query: extended:0 query:"SELECT pg_catalog.pg_is_in_recovery()" 2025-09-22 11:11:52.570: sr_check_worker pid 903049: DEBUG: verify_backend_node_status: there's no primary node 2025-09-22 11:11:52.570: sr_check_worker pid 903049: DEBUG: node status[0]: 0 2025-09-22 11:11:52.570: sr_check_worker pid 903049: DEBUG: node status[1]: 2 2025-09-22 11:11:52.570: sr_check_worker pid 903049: DEBUG: pool_release_follow_primary_lock called 2025-09-22 11:11:52.959: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:52.960: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:52.961: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:11:52.970: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:11:52.970: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:11:52.970: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:52.970: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:52.970: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:52.971: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:54.971: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:56.972: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:11:57.563: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = TIMEOUT Current State = LEADER 2025-09-22 11:11:57.563: watchdog pid 902555: DEBUG: sending packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24559] type:[IAM COORDINATOR] state:[LEADER] 2025-09-22 11:11:57.563: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[M], command ID:24559, data Length:124 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: received watchdog packet type:I 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: reading packet type I of length 369 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24559] type:[NODE INFO] state:[LEADER] 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: packet I with command ID 24559 is reply to the command M 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: Watchdog node "192.168.1.72:9999 Linux localhost.localdomain" has replied for command id 24559 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: command I with command id 24559 is finished with COMMAND_FINISHED_ALL_REPLIED 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = COMMAND FINISHED Current State = LEADER 2025-09-22 11:11:57.564: watchdog pid 902555: DEBUG: I am the cluster leader node command finished with status:[ALL NODES REPLIED] 2025-09-22 11:11:57.564: watchdog pid 902555: DETAIL: The command was sent to 1 nodes and 1 nodes replied to it 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: received watchdog packet type:d 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: reading packet type d of length 62 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: STATE MACHINE INVOKED WITH EVENT = PACKET RECEIVED Current State = LEADER 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: received packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24956] type:[DATA REQUEST FOR LEADER] state:[LEADER] 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: sending packet, watchdog node:[192.168.1.72:9999 Linux localhost.localdomain] command id:[24956] type:[DATA] state:[LEADER] 2025-09-22 11:11:57.573: watchdog pid 902555: DEBUG: sending watchdog packet to socket:7, type:[D], command ID:24956, data Length:110 2025-09-22 11:11:57.971: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:57.971: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:11:57.973: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:11:57.981: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:11:57.981: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:11:57.981: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:11:57.981: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:57.981: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:11:58.972: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:12:00.972: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:12:02.570: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:12:02.570: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:12:02.570: sr_check_worker pid 903049: DEBUG: watchdog status: 4 2025-09-22 11:12:02.570: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:12:02.571: watchdog pid 902555: DEBUG: received the get data request from local pgpool-II on IPC interface 2025-09-22 11:12:02.571: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:0 2025-09-22 11:12:02.571: sr_check_worker pid 903049: DEBUG: 1:0: Unexpected 2025-09-22 11:12:02.571: watchdog pid 902555: DEBUG: new IPC connection received 2025-09-22 11:12:02.571: watchdog pid 902555: DEBUG: sending watchdog packet to socket:9, type:[7], command ID:0, data Length:34 2025-09-22 11:12:02.571: sr_check_worker pid 903049: DEBUG: quorum: 1 node_count: -1 2025-09-22 11:12:02.571: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: lock was not held by anyone 2025-09-22 11:12:02.571: sr_check_worker pid 903049: DEBUG: pool_acquire_follow_primary_lock: succeeded in acquiring lock 2025-09-22 11:12:02.571: sr_check_worker pid 903049: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:12:02.572: sr_check_worker pid 903049: DEBUG: authenticate kind = 10 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: SCRAM authentication successful for user:rep 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: authenticate backend: key data received 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: do_query: extended:0 query:"SELECT pg_catalog.pg_is_in_recovery()" 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: verify_backend_node_status: there's no primary node 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: node status[0]: 0 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: node status[1]: 2 2025-09-22 11:12:02.581: sr_check_worker pid 903049: DEBUG: pool_release_follow_primary_lock called 2025-09-22 11:12:02.972: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:12:02.981: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:12:02.982: health_check1 pid 902636: DEBUG: SSL is requested but SSL support is not available 2025-09-22 11:12:02.983: health_check1 pid 902636: DEBUG: authenticate kind = 10 2025-09-22 11:12:02.992: health_check1 pid 902636: DEBUG: SCRAM authentication successful for user:pgpool 2025-09-22 11:12:02.992: health_check1 pid 902636: DEBUG: authenticate backend: key data received 2025-09-22 11:12:02.992: health_check1 pid 902636: DEBUG: authenticate backend: transaction state: I 2025-09-22 11:12:02.992: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:12:02.992: health_check1 pid 902636: DEBUG: health check: clearing alarm 2025-09-22 11:12:04.973: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694 2025-09-22 11:12:06.973: heart_beat_sender pid 902601: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.1.72:9694根据pgpool日志,排除错误,写出详细故障处理步骤
最新发布
09-23
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值