Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
aports
aports
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 650
    • Issues 650
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 212
    • Merge Requests 212
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • alpine
  • aportsaports
  • Issues
  • #8019

Closed
Open
Opened Oct 18, 2017 by algitbot@rootOwner

Busybox syslogd truncates messages at ~250 characters

As the title says: When you log messages with syslogd they are cut off after about 250 chars.

To verify try this:

# syslogd
# logger "This manual page documents the GNU version of find. GNU find searches the directory tree rooted at each given file name by evaluating the given expression from left to right, according to the rules of precedence (see section OPERATORS), until the outcome is known (the left hand side is false for and operations, true for or), at which point find moves on to the next file name."
# cat /var/log/messages
Oct 18 09:42:20 syslogd started: BusyBox v1.26.2
Oct 18 10:24:31 91ccfe953917 user.notice root: This manual page documents the GNU version of find. GNU find searches the directory tree rooted at each given file name by evaluating the given expression from left to right, according to the rules of precedence (see section OPER

There’s a similar bug report over at Ubuntu’s launchpad which seems to indicate that this is due to a compile time config variable CONFIG_FEATURE_SYSLOGD_READ_BUFFER_SIZE which defaults to 256. They fixed it by increasing it to 512. Preferrably it should be set even higher, e.g. 1024 to be on the safe side.

(from redmine: issue id 8019, created on 2017-10-18)

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
3.12.1
Milestone
3.12.1 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: alpine/aports#8019